Version in base suite: 13.13-0+deb11u1 Base version: postgresql-13_13.13-0+deb11u1 Target version: postgresql-13_13.14-0+deb11u1 Base file: /srv/ftp-master.debian.org/ftp/pool/main/p/postgresql-13/postgresql-13_13.13-0+deb11u1.dsc Target file: /srv/ftp-master.debian.org/policy/pool/main/p/postgresql-13/postgresql-13_13.14-0+deb11u1.dsc .gitrevision | 2 COPYRIGHT | 2 configure | 20 configure.in | 4 contrib/intarray/_int_gist.c | 10 contrib/intarray/data/test__int.data | 1 contrib/intarray/expected/_int.out | 33 contrib/intarray/sql/_int.sql | 5 contrib/pageinspect/expected/hash.out | 5 contrib/pageinspect/hashfuncs.c | 6 contrib/pageinspect/sql/hash.sql | 5 contrib/pgcrypto/pgp-decrypt.c | 3 contrib/pgstattuple/expected/pgstattuple.out | 11 contrib/pgstattuple/pgstatindex.c | 5 contrib/pgstattuple/sql/pgstattuple.sql | 2 contrib/xml2/xpath.c | 1 debian/changelog | 19 doc/src/sgml/ddl.sgml | 39 doc/src/sgml/fdwhandler.sgml | 17 doc/src/sgml/high-availability.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 | 4 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 | 4 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 | 24 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 | 10 doc/src/sgml/html/ddl-priv.html | 17 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 | 15 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 | 4 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 | 4 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 | 33 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 | 6 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 | 8 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/legalnotice.html | 2 doc/src/sgml/html/libpq-async.html | 11 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 | 7 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 | 6 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 | 15 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 | 9 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 | 4 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 | 14 doc/src/sgml/html/release-13-13.html | 12 doc/src/sgml/html/release-13-14.html | 302 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 | 4 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 | 6 doc/src/sgml/html/sql-alterextension.html | 4 doc/src/sgml/html/sql-alterforeigndatawrapper.html | 6 doc/src/sgml/html/sql-alterforeigntable.html | 4 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 | 12 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 | 4 doc/src/sgml/html/sql-createsubscription.html | 4 doc/src/sgml/html/sql-createtable.html | 41 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 | 4 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 | 7 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 | 6 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 | 4 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 | 6 doc/src/sgml/html/wal.html | 4 doc/src/sgml/html/warm-standby-failover.html | 4 doc/src/sgml/html/warm-standby.html | 6 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/indices.sgml | 35 doc/src/sgml/information_schema.sgml | 4 doc/src/sgml/legal.sgml | 6 doc/src/sgml/libpq.sgml | 7 doc/src/sgml/logical-replication.sgml | 3 doc/src/sgml/man1/clusterdb.1 | 8 doc/src/sgml/man1/createdb.1 | 8 doc/src/sgml/man1/createuser.1 | 8 doc/src/sgml/man1/dropdb.1 | 8 doc/src/sgml/man1/dropuser.1 | 8 doc/src/sgml/man1/ecpg.1 | 8 doc/src/sgml/man1/initdb.1 | 8 doc/src/sgml/man1/oid2name.1 | 8 doc/src/sgml/man1/pg_archivecleanup.1 | 8 doc/src/sgml/man1/pg_basebackup.1 | 8 doc/src/sgml/man1/pg_checksums.1 | 8 doc/src/sgml/man1/pg_config.1 | 8 doc/src/sgml/man1/pg_controldata.1 | 8 doc/src/sgml/man1/pg_ctl.1 | 8 doc/src/sgml/man1/pg_dump.1 | 8 doc/src/sgml/man1/pg_dumpall.1 | 8 doc/src/sgml/man1/pg_isready.1 | 8 doc/src/sgml/man1/pg_receivewal.1 | 8 doc/src/sgml/man1/pg_recvlogical.1 | 8 doc/src/sgml/man1/pg_resetwal.1 | 8 doc/src/sgml/man1/pg_restore.1 | 8 doc/src/sgml/man1/pg_rewind.1 | 8 doc/src/sgml/man1/pg_standby.1 | 8 doc/src/sgml/man1/pg_test_fsync.1 | 8 doc/src/sgml/man1/pg_test_timing.1 | 8 doc/src/sgml/man1/pg_upgrade.1 | 8 doc/src/sgml/man1/pg_verifybackup.1 | 8 doc/src/sgml/man1/pg_waldump.1 | 8 doc/src/sgml/man1/pgbench.1 | 8 doc/src/sgml/man1/postgres.1 | 8 doc/src/sgml/man1/postmaster.1 | 8 doc/src/sgml/man1/psql.1 | 10 doc/src/sgml/man1/reindexdb.1 | 8 doc/src/sgml/man1/vacuumdb.1 | 8 doc/src/sgml/man1/vacuumlo.1 | 8 doc/src/sgml/man3/SPI_commit.3 | 8 doc/src/sgml/man3/SPI_connect.3 | 8 doc/src/sgml/man3/SPI_copytuple.3 | 8 doc/src/sgml/man3/SPI_cursor_close.3 | 8 doc/src/sgml/man3/SPI_cursor_fetch.3 | 8 doc/src/sgml/man3/SPI_cursor_find.3 | 8 doc/src/sgml/man3/SPI_cursor_move.3 | 8 doc/src/sgml/man3/SPI_cursor_open.3 | 8 doc/src/sgml/man3/SPI_cursor_open_with_args.3 | 8 doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 | 8 doc/src/sgml/man3/SPI_exec.3 | 8 doc/src/sgml/man3/SPI_execp.3 | 8 doc/src/sgml/man3/SPI_execute.3 | 8 doc/src/sgml/man3/SPI_execute_plan.3 | 8 doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 | 8 doc/src/sgml/man3/SPI_execute_with_args.3 | 8 doc/src/sgml/man3/SPI_finish.3 | 8 doc/src/sgml/man3/SPI_fname.3 | 8 doc/src/sgml/man3/SPI_fnumber.3 | 8 doc/src/sgml/man3/SPI_freeplan.3 | 8 doc/src/sgml/man3/SPI_freetuple.3 | 8 doc/src/sgml/man3/SPI_freetuptable.3 | 8 doc/src/sgml/man3/SPI_getargcount.3 | 8 doc/src/sgml/man3/SPI_getargtypeid.3 | 8 doc/src/sgml/man3/SPI_getbinval.3 | 8 doc/src/sgml/man3/SPI_getnspname.3 | 8 doc/src/sgml/man3/SPI_getrelname.3 | 8 doc/src/sgml/man3/SPI_gettype.3 | 8 doc/src/sgml/man3/SPI_gettypeid.3 | 8 doc/src/sgml/man3/SPI_getvalue.3 | 8 doc/src/sgml/man3/SPI_is_cursor_plan.3 | 8 doc/src/sgml/man3/SPI_keepplan.3 | 8 doc/src/sgml/man3/SPI_modifytuple.3 | 8 doc/src/sgml/man3/SPI_palloc.3 | 8 doc/src/sgml/man3/SPI_pfree.3 | 8 doc/src/sgml/man3/SPI_prepare.3 | 8 doc/src/sgml/man3/SPI_prepare_cursor.3 | 8 doc/src/sgml/man3/SPI_prepare_params.3 | 8 doc/src/sgml/man3/SPI_register_relation.3 | 8 doc/src/sgml/man3/SPI_register_trigger_data.3 | 8 doc/src/sgml/man3/SPI_repalloc.3 | 8 doc/src/sgml/man3/SPI_result_code_string.3 | 8 doc/src/sgml/man3/SPI_returntuple.3 | 8 doc/src/sgml/man3/SPI_rollback.3 | 8 doc/src/sgml/man3/SPI_saveplan.3 | 8 doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 | 8 doc/src/sgml/man3/SPI_scroll_cursor_move.3 | 8 doc/src/sgml/man3/SPI_start_transaction.3 | 8 doc/src/sgml/man3/SPI_unregister_relation.3 | 8 doc/src/sgml/man3/dblink.3 | 8 doc/src/sgml/man3/dblink_build_sql_delete.3 | 8 doc/src/sgml/man3/dblink_build_sql_insert.3 | 8 doc/src/sgml/man3/dblink_build_sql_update.3 | 8 doc/src/sgml/man3/dblink_cancel_query.3 | 8 doc/src/sgml/man3/dblink_close.3 | 8 doc/src/sgml/man3/dblink_connect.3 | 8 doc/src/sgml/man3/dblink_connect_u.3 | 8 doc/src/sgml/man3/dblink_disconnect.3 | 8 doc/src/sgml/man3/dblink_error_message.3 | 8 doc/src/sgml/man3/dblink_exec.3 | 8 doc/src/sgml/man3/dblink_fetch.3 | 8 doc/src/sgml/man3/dblink_get_connections.3 | 8 doc/src/sgml/man3/dblink_get_notify.3 | 8 doc/src/sgml/man3/dblink_get_pkey.3 | 8 doc/src/sgml/man3/dblink_get_result.3 | 8 doc/src/sgml/man3/dblink_is_busy.3 | 8 doc/src/sgml/man3/dblink_open.3 | 8 doc/src/sgml/man3/dblink_send_query.3 | 8 doc/src/sgml/man7/ABORT.7 | 8 doc/src/sgml/man7/ALTER_AGGREGATE.7 | 8 doc/src/sgml/man7/ALTER_COLLATION.7 | 8 doc/src/sgml/man7/ALTER_CONVERSION.7 | 8 doc/src/sgml/man7/ALTER_DATABASE.7 | 8 doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 | 8 doc/src/sgml/man7/ALTER_DOMAIN.7 | 8 doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 | 10 doc/src/sgml/man7/ALTER_EXTENSION.7 | 8 doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 | 10 doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 | 8 doc/src/sgml/man7/ALTER_FUNCTION.7 | 8 doc/src/sgml/man7/ALTER_GROUP.7 | 8 doc/src/sgml/man7/ALTER_INDEX.7 | 8 doc/src/sgml/man7/ALTER_LANGUAGE.7 | 8 doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 | 8 doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 | 8 doc/src/sgml/man7/ALTER_OPERATOR.7 | 8 doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 | 8 doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 | 8 doc/src/sgml/man7/ALTER_POLICY.7 | 8 doc/src/sgml/man7/ALTER_PROCEDURE.7 | 8 doc/src/sgml/man7/ALTER_PUBLICATION.7 | 8 doc/src/sgml/man7/ALTER_ROLE.7 | 8 doc/src/sgml/man7/ALTER_ROUTINE.7 | 8 doc/src/sgml/man7/ALTER_RULE.7 | 8 doc/src/sgml/man7/ALTER_SCHEMA.7 | 8 doc/src/sgml/man7/ALTER_SEQUENCE.7 | 8 doc/src/sgml/man7/ALTER_SERVER.7 | 8 doc/src/sgml/man7/ALTER_STATISTICS.7 | 8 doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 | 8 doc/src/sgml/man7/ALTER_SYSTEM.7 | 8 doc/src/sgml/man7/ALTER_TABLE.7 | 8 doc/src/sgml/man7/ALTER_TABLESPACE.7 | 8 doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 | 8 doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 | 8 doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 | 8 doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 | 8 doc/src/sgml/man7/ALTER_TRIGGER.7 | 8 doc/src/sgml/man7/ALTER_TYPE.7 | 8 doc/src/sgml/man7/ALTER_USER.7 | 8 doc/src/sgml/man7/ALTER_USER_MAPPING.7 | 8 doc/src/sgml/man7/ALTER_VIEW.7 | 8 doc/src/sgml/man7/ANALYZE.7 | 8 doc/src/sgml/man7/BEGIN.7 | 8 doc/src/sgml/man7/CALL.7 | 8 doc/src/sgml/man7/CHECKPOINT.7 | 8 doc/src/sgml/man7/CLOSE.7 | 8 doc/src/sgml/man7/CLUSTER.7 | 8 doc/src/sgml/man7/COMMENT.7 | 8 doc/src/sgml/man7/COMMIT.7 | 8 doc/src/sgml/man7/COMMIT_PREPARED.7 | 8 doc/src/sgml/man7/COPY.7 | 12 doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 | 8 doc/src/sgml/man7/CREATE_AGGREGATE.7 | 8 doc/src/sgml/man7/CREATE_CAST.7 | 8 doc/src/sgml/man7/CREATE_COLLATION.7 | 8 doc/src/sgml/man7/CREATE_CONVERSION.7 | 8 doc/src/sgml/man7/CREATE_DATABASE.7 | 8 doc/src/sgml/man7/CREATE_DOMAIN.7 | 8 doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 | 8 doc/src/sgml/man7/CREATE_EXTENSION.7 | 8 doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 | 8 doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 | 8 doc/src/sgml/man7/CREATE_FUNCTION.7 | 8 doc/src/sgml/man7/CREATE_GROUP.7 | 8 doc/src/sgml/man7/CREATE_INDEX.7 | 8 doc/src/sgml/man7/CREATE_LANGUAGE.7 | 8 doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 | 8 doc/src/sgml/man7/CREATE_OPERATOR.7 | 8 doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 | 8 doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 | 8 doc/src/sgml/man7/CREATE_POLICY.7 | 8 doc/src/sgml/man7/CREATE_PROCEDURE.7 | 8 doc/src/sgml/man7/CREATE_PUBLICATION.7 | 8 doc/src/sgml/man7/CREATE_ROLE.7 | 8 doc/src/sgml/man7/CREATE_RULE.7 | 8 doc/src/sgml/man7/CREATE_SCHEMA.7 | 8 doc/src/sgml/man7/CREATE_SEQUENCE.7 | 8 doc/src/sgml/man7/CREATE_SERVER.7 | 8 doc/src/sgml/man7/CREATE_STATISTICS.7 | 8 doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 | 8 doc/src/sgml/man7/CREATE_TABLE.7 | 17 doc/src/sgml/man7/CREATE_TABLESPACE.7 | 8 doc/src/sgml/man7/CREATE_TABLE_AS.7 | 8 doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 | 8 doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 | 8 doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 | 8 doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 | 8 doc/src/sgml/man7/CREATE_TRANSFORM.7 | 8 doc/src/sgml/man7/CREATE_TRIGGER.7 | 8 doc/src/sgml/man7/CREATE_TYPE.7 | 8 doc/src/sgml/man7/CREATE_USER.7 | 8 doc/src/sgml/man7/CREATE_USER_MAPPING.7 | 8 doc/src/sgml/man7/CREATE_VIEW.7 | 8 doc/src/sgml/man7/DEALLOCATE.7 | 8 doc/src/sgml/man7/DECLARE.7 | 8 doc/src/sgml/man7/DELETE.7 | 8 doc/src/sgml/man7/DISCARD.7 | 8 doc/src/sgml/man7/DO.7 | 8 doc/src/sgml/man7/DROP_ACCESS_METHOD.7 | 8 doc/src/sgml/man7/DROP_AGGREGATE.7 | 8 doc/src/sgml/man7/DROP_CAST.7 | 8 doc/src/sgml/man7/DROP_COLLATION.7 | 8 doc/src/sgml/man7/DROP_CONVERSION.7 | 8 doc/src/sgml/man7/DROP_DATABASE.7 | 8 doc/src/sgml/man7/DROP_DOMAIN.7 | 8 doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 | 8 doc/src/sgml/man7/DROP_EXTENSION.7 | 8 doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 | 8 doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 | 8 doc/src/sgml/man7/DROP_FUNCTION.7 | 8 doc/src/sgml/man7/DROP_GROUP.7 | 8 doc/src/sgml/man7/DROP_INDEX.7 | 8 doc/src/sgml/man7/DROP_LANGUAGE.7 | 8 doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 | 8 doc/src/sgml/man7/DROP_OPERATOR.7 | 8 doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 | 8 doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 | 8 doc/src/sgml/man7/DROP_OWNED.7 | 8 doc/src/sgml/man7/DROP_POLICY.7 | 8 doc/src/sgml/man7/DROP_PROCEDURE.7 | 8 doc/src/sgml/man7/DROP_PUBLICATION.7 | 8 doc/src/sgml/man7/DROP_ROLE.7 | 8 doc/src/sgml/man7/DROP_ROUTINE.7 | 8 doc/src/sgml/man7/DROP_RULE.7 | 8 doc/src/sgml/man7/DROP_SCHEMA.7 | 8 doc/src/sgml/man7/DROP_SEQUENCE.7 | 8 doc/src/sgml/man7/DROP_SERVER.7 | 8 doc/src/sgml/man7/DROP_STATISTICS.7 | 8 doc/src/sgml/man7/DROP_SUBSCRIPTION.7 | 8 doc/src/sgml/man7/DROP_TABLE.7 | 8 doc/src/sgml/man7/DROP_TABLESPACE.7 | 8 doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 | 8 doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 | 8 doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 | 8 doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 | 8 doc/src/sgml/man7/DROP_TRANSFORM.7 | 8 doc/src/sgml/man7/DROP_TRIGGER.7 | 8 doc/src/sgml/man7/DROP_TYPE.7 | 8 doc/src/sgml/man7/DROP_USER.7 | 8 doc/src/sgml/man7/DROP_USER_MAPPING.7 | 8 doc/src/sgml/man7/DROP_VIEW.7 | 8 doc/src/sgml/man7/END.7 | 8 doc/src/sgml/man7/EXECUTE.7 | 8 doc/src/sgml/man7/EXPLAIN.7 | 8 doc/src/sgml/man7/FETCH.7 | 8 doc/src/sgml/man7/GRANT.7 | 8 doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 | 8 doc/src/sgml/man7/INSERT.7 | 8 doc/src/sgml/man7/LISTEN.7 | 8 doc/src/sgml/man7/LOAD.7 | 8 doc/src/sgml/man7/LOCK.7 | 8 doc/src/sgml/man7/MOVE.7 | 8 doc/src/sgml/man7/NOTIFY.7 | 8 doc/src/sgml/man7/PREPARE.7 | 8 doc/src/sgml/man7/PREPARE_TRANSACTION.7 | 8 doc/src/sgml/man7/REASSIGN_OWNED.7 | 8 doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 | 8 doc/src/sgml/man7/REINDEX.7 | 8 doc/src/sgml/man7/RELEASE_SAVEPOINT.7 | 8 doc/src/sgml/man7/RESET.7 | 8 doc/src/sgml/man7/REVOKE.7 | 8 doc/src/sgml/man7/ROLLBACK.7 | 8 doc/src/sgml/man7/ROLLBACK_PREPARED.7 | 8 doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 | 8 doc/src/sgml/man7/SAVEPOINT.7 | 8 doc/src/sgml/man7/SECURITY_LABEL.7 | 8 doc/src/sgml/man7/SELECT.7 | 11 doc/src/sgml/man7/SELECT_INTO.7 | 8 doc/src/sgml/man7/SET.7 | 8 doc/src/sgml/man7/SET_CONSTRAINTS.7 | 8 doc/src/sgml/man7/SET_ROLE.7 | 8 doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 | 8 doc/src/sgml/man7/SET_TRANSACTION.7 | 8 doc/src/sgml/man7/SHOW.7 | 8 doc/src/sgml/man7/START_TRANSACTION.7 | 8 doc/src/sgml/man7/TRUNCATE.7 | 8 doc/src/sgml/man7/UNLISTEN.7 | 8 doc/src/sgml/man7/UPDATE.7 | 8 doc/src/sgml/man7/VACUUM.7 | 8 doc/src/sgml/man7/VALUES.7 | 8 doc/src/sgml/plpython.sgml | 2 doc/src/sgml/protocol.sgml | 18 doc/src/sgml/ref/alter_event_trigger.sgml | 2 doc/src/sgml/ref/alter_foreign_data_wrapper.sgml | 2 doc/src/sgml/ref/copy.sgml | 8 doc/src/sgml/ref/create_table.sgml | 19 doc/src/sgml/ref/select.sgml | 3 doc/src/sgml/release-13.sgml | 945 ++ doc/src/sgml/syntax.sgml | 12 doc/src/sgml/wal.sgml | 2 src/backend/access/gin/ginbtree.c | 74 src/backend/access/heap/heapam.c | 41 src/backend/access/heap/hio.c | 2 src/backend/access/spgist/spgutils.c | 29 src/backend/access/transam/twophase.c | 2 src/backend/access/transam/xact.c | 1 src/backend/access/transam/xlog.c | 6 src/backend/catalog/aclchk.c | 4 src/backend/catalog/heap.c | 7 src/backend/commands/alter.c | 17 src/backend/commands/copy.c | 6 src/backend/commands/indexcmds.c | 36 src/backend/commands/matview.c | 40 src/backend/commands/statscmds.c | 39 src/backend/commands/tablecmds.c | 68 src/backend/commands/tsearchcmds.c | 95 src/backend/executor/nodeHash.c | 13 src/backend/jit/llvm/llvmjit.c | 141 src/backend/jit/llvm/llvmjit_deform.c | 77 src/backend/jit/llvm/llvmjit_expr.c | 62 src/backend/jit/llvm/llvmjit_inline.cpp | 38 src/backend/libpq/auth.c | 13 src/backend/libpq/be-secure-gssapi.c | 60 src/backend/libpq/be-secure-openssl.c | 26 src/backend/libpq/pqcomm.c | 22 src/backend/optimizer/prep/prepjointree.c | 9 src/backend/optimizer/util/clauses.c | 66 src/backend/optimizer/util/pathnode.c | 175 src/backend/po/de.po | 2 src/backend/po/es.po | 2 src/backend/po/fr.po | 2 src/backend/po/it.po | 2 src/backend/po/ja.po | 671 - src/backend/po/ko.po | 2 src/backend/po/ru.po | 2 src/backend/po/sv.po | 2 src/backend/po/tr.po | 2 src/backend/po/uk.po | 2078 ++--- src/backend/po/zh_CN.po | 2 src/backend/port/win32/socket.c | 1 src/backend/replication/libpqwalreceiver/libpqwalreceiver.c | 6 src/backend/replication/logical/tablesync.c | 20 src/backend/storage/ipc/procarray.c | 3 src/backend/storage/lmgr/lwlock.c | 55 src/backend/storage/lmgr/proc.c | 4 src/backend/utils/adt/timestamp.c | 97 src/backend/utils/adt/xml.c | 14 src/backend/utils/cache/catcache.c | 299 src/backend/utils/error/elog.c | 4 src/backend/utils/misc/guc.c | 11 src/bin/pg_ctl/pg_ctl.c | 4 src/bin/pg_dump/pg_dump.c | 52 src/bin/pg_dump/pg_dump.h | 1 src/bin/pg_dump/t/002_pg_dump.pl | 6 src/bin/pg_rewind/t/003_extrafiles.pl | 13 src/bin/pg_upgrade/po/uk.po | 240 src/bin/pg_waldump/po/de.po | 4 src/bin/psql/po/ja.po | 4 src/bin/scripts/po/uk.po | 93 src/include/access/tableam.h | 4 src/include/common/int.h | 6 src/include/jit/llvmjit.h | 8 src/include/jit/llvmjit_emit.h | 30 src/include/optimizer/optimizer.h | 2 src/include/pg_config.h.in | 3 src/include/port/atomics/generic.h | 2 src/include/storage/buf_internals.h | 2 src/include/storage/lwlock.h | 8 src/include/storage/proc.h | 2 src/interfaces/libpq/fe-secure-gssapi.c | 62 src/interfaces/libpq/fe-secure-openssl.c | 102 src/interfaces/libpq/fe-secure.c | 7 src/interfaces/libpq/libpq-int.h | 4 src/pl/plperl/GNUmakefile | 4 src/pl/plperl/plperl.h | 194 src/pl/plperl/plperl_system.h | 214 src/pl/plpython/Makefile | 3 src/pl/plpython/plpython.h | 104 src/pl/plpython/plpython_system.h | 134 src/test/modules/test_pg_dump/t/001_base.pl | 31 src/test/modules/test_pg_dump/test_pg_dump--1.0.sql | 2 src/test/regress/expected/fast_default.out | 18 src/test/regress/expected/generated.out | 3 src/test/regress/expected/horology.out | 4 src/test/regress/expected/indexing.out | 39 src/test/regress/expected/inherit.out | 17 src/test/regress/expected/int8.out | 2 src/test/regress/expected/interval.out | 13 src/test/regress/expected/join.out | 26 src/test/regress/expected/matview.out | 16 src/test/regress/expected/opr_sanity.out | 2 src/test/regress/expected/partition_join.out | 167 src/test/regress/expected/tsdicts.out | 34 src/test/regress/pg_regress.c | 2 src/test/regress/sql/fast_default.sql | 11 src/test/regress/sql/generated.sql | 3 src/test/regress/sql/horology.sql | 2 src/test/regress/sql/indexing.sql | 20 src/test/regress/sql/inherit.sql | 9 src/test/regress/sql/int8.sql | 1 src/test/regress/sql/interval.sql | 8 src/test/regress/sql/join.sql | 12 src/test/regress/sql/matview.sql | 17 src/test/regress/sql/opr_sanity.sql | 2 src/test/regress/sql/partition_join.sql | 48 src/test/regress/sql/tsdicts.sql | 30 src/timezone/data/tzdata.zi | 3961 +++++----- src/tools/msvc/Solution.pm | 2 src/tools/pgindent/typedefs.list | 1 1559 files changed, 10923 insertions(+), 8069 deletions(-) diff -Nru postgresql-13-13.13/.gitrevision postgresql-13-13.14/.gitrevision --- postgresql-13-13.13/.gitrevision 2023-11-06 22:29:29.000000000 +0000 +++ postgresql-13-13.14/.gitrevision 2024-02-05 22:03:10.000000000 +0000 @@ -1 +1 @@ -319310aa121285b1c7c036cb956a11bcc9d1bcb2 +b3b2bf3b9cc1f31170d3b4e21cb6ac0cf24bf90a diff -Nru postgresql-13-13.13/COPYRIGHT postgresql-13-13.14/COPYRIGHT --- postgresql-13-13.13/COPYRIGHT 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/COPYRIGHT 2024-02-05 21:47:02.000000000 +0000 @@ -1,7 +1,7 @@ PostgreSQL Database Management System (formerly known as Postgres, then as Postgres95) -Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group +Portions Copyright (c) 1996-2024, PostgreSQL Global Development Group Portions Copyright (c) 1994, The Regents of the University of California diff -Nru postgresql-13-13.13/configure postgresql-13-13.14/configure --- postgresql-13-13.13/configure 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/configure 2024-02-05 21:47:02.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.13. +# Generated by GNU Autoconf 2.69 for PostgreSQL 13.14. # # Report bugs to . # @@ -582,8 +582,8 @@ # Identity of this package. PACKAGE_NAME='PostgreSQL' PACKAGE_TARNAME='postgresql' -PACKAGE_VERSION='13.13' -PACKAGE_STRING='PostgreSQL 13.13' +PACKAGE_VERSION='13.14' +PACKAGE_STRING='PostgreSQL 13.14' 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.13 to adapt to many kinds of systems. +\`configure' configures PostgreSQL 13.14 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.13:";; + short | recursive ) echo "Configuration of PostgreSQL 13.14:";; 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.13 +PostgreSQL configure 13.14 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.13, which was +It was created by PostgreSQL $as_me 13.14, which was generated by GNU Autoconf 2.69. Invocation command line was $ $0 $@ @@ -12713,7 +12713,7 @@ # defines OPENSSL_VERSION_NUMBER to claim version 2.0.0, even though it # doesn't have these OpenSSL 1.1.0 functions. So check for individual # functions. - for ac_func in OPENSSL_init_ssl BIO_get_data BIO_meth_new ASN1_STRING_get0_data + for ac_func in OPENSSL_init_ssl BIO_meth_new ASN1_STRING_get0_data do : as_ac_var=`$as_echo "ac_cv_func_$ac_func" | $as_tr_sh` ac_fn_c_check_func "$LINENO" "$ac_func" "$as_ac_var" @@ -20037,7 +20037,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.13, which was +This file was extended by PostgreSQL $as_me 13.14, which was generated by GNU Autoconf 2.69. Invocation command line was CONFIG_FILES = $CONFIG_FILES @@ -20108,7 +20108,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.13 +PostgreSQL config.status 13.14 configured by $0, generated by GNU Autoconf 2.69, with options \\"\$ac_cs_config\\" diff -Nru postgresql-13-13.13/configure.in postgresql-13-13.14/configure.in --- postgresql-13-13.13/configure.in 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/configure.in 2024-02-05 21:47:02.000000000 +0000 @@ -17,7 +17,7 @@ dnl m4_pattern_forbid(^PGAC_)dnl to catch undefined macros -AC_INIT([PostgreSQL], [13.13], [pgsql-bugs@lists.postgresql.org], [], [https://www.postgresql.org/]) +AC_INIT([PostgreSQL], [13.14], [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 @@ -1275,7 +1275,7 @@ # defines OPENSSL_VERSION_NUMBER to claim version 2.0.0, even though it # doesn't have these OpenSSL 1.1.0 functions. So check for individual # functions. - AC_CHECK_FUNCS([OPENSSL_init_ssl BIO_get_data BIO_meth_new ASN1_STRING_get0_data]) + AC_CHECK_FUNCS([OPENSSL_init_ssl BIO_meth_new ASN1_STRING_get0_data]) # OpenSSL versions before 1.1.0 required setting callback functions, for # thread-safety. In 1.1.0, it's no longer required, and CRYPTO_lock() # function was removed. diff -Nru postgresql-13-13.13/contrib/intarray/_int_gist.c postgresql-13-13.14/contrib/intarray/_int_gist.c --- postgresql-13-13.13/contrib/intarray/_int_gist.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/intarray/_int_gist.c 2024-02-05 21:47:02.000000000 +0000 @@ -290,8 +290,7 @@ ArrayType *in; int lenin; int *din; - int i, - j; + int i; in = DatumGetArrayTypeP(entry->key); @@ -335,9 +334,12 @@ dr = ARRPTR(r); for (i = 0; i < lenin; i += 2) - for (j = din[i]; j <= din[i + 1]; j++) + { + /* use int64 for j in case din[i + 1] is INT_MAX */ + for (int64 j = din[i]; j <= din[i + 1]; j++) if ((!i) || *(dr - 1) != j) - *dr++ = j; + *dr++ = (int) j; + } if (in != (ArrayType *) DatumGetPointer(entry->key)) pfree(in); diff -Nru postgresql-13-13.13/contrib/intarray/data/test__int.data postgresql-13-13.14/contrib/intarray/data/test__int.data --- postgresql-13-13.13/contrib/intarray/data/test__int.data 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/intarray/data/test__int.data 2024-02-05 21:47:02.000000000 +0000 @@ -6998,3 +6998,4 @@ {173,208,229} {6,22,142,267,299} {22,122,173,245,293} +{1,2,101,102,201,202,2147483647} diff -Nru postgresql-13-13.13/contrib/intarray/expected/_int.out postgresql-13-13.14/contrib/intarray/expected/_int.out --- postgresql-13-13.13/contrib/intarray/expected/_int.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/intarray/expected/_int.out 2024-02-05 21:47:02.000000000 +0000 @@ -464,13 +464,13 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from test__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) SET enable_seqscan = off; -- not all of these would use index by default @@ -538,13 +538,13 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from test__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) INSERT INTO test__int SELECT array(SELECT x FROM generate_series(1, 1001) x); -- should fail @@ -620,13 +620,13 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from test__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) DROP INDEX text_idx; @@ -700,13 +700,13 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from test__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) DROP INDEX text_idx; @@ -774,13 +774,13 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from test__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) DROP INDEX text_idx; @@ -848,13 +848,13 @@ SELECT count(*) from test__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from test__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) DROP INDEX text_idx; @@ -870,9 +870,10 @@ -- core that would reach the same codepaths. CREATE TABLE more__int AS SELECT -- Leave alone NULLs, empty arrays and the one row that we use to test - -- equality + -- equality; also skip INT_MAX CASE WHEN a IS NULL OR a = '{}' OR a = '{73,23,20}' THEN a ELSE - (select array_agg(u) || array_agg(u + 1000) || array_agg(u + 2000) from (select unnest(a) u) x) + (select array_agg(u) || array_agg(u + 1000) || array_agg(u + 2000) + from unnest(a) u where u < 2000000000) END AS a, a as b FROM test__int; CREATE INDEX ON more__int using gist (a gist__int_ops(numranges = 252)); @@ -939,13 +940,13 @@ SELECT count(*) from more__int WHERE a @@ '20 | !21'; count ------- - 6566 + 6567 (1 row) SELECT count(*) from more__int WHERE a @@ '!20 & !21'; count ------- - 6343 + 6344 (1 row) RESET enable_seqscan; diff -Nru postgresql-13-13.13/contrib/intarray/sql/_int.sql postgresql-13-13.14/contrib/intarray/sql/_int.sql --- postgresql-13-13.13/contrib/intarray/sql/_int.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/intarray/sql/_int.sql 2024-02-05 21:47:02.000000000 +0000 @@ -194,9 +194,10 @@ -- core that would reach the same codepaths. CREATE TABLE more__int AS SELECT -- Leave alone NULLs, empty arrays and the one row that we use to test - -- equality + -- equality; also skip INT_MAX CASE WHEN a IS NULL OR a = '{}' OR a = '{73,23,20}' THEN a ELSE - (select array_agg(u) || array_agg(u + 1000) || array_agg(u + 2000) from (select unnest(a) u) x) + (select array_agg(u) || array_agg(u + 1000) || array_agg(u + 2000) + from unnest(a) u where u < 2000000000) END AS a, a as b FROM test__int; CREATE INDEX ON more__int using gist (a gist__int_ops(numranges = 252)); diff -Nru postgresql-13-13.13/contrib/pageinspect/expected/hash.out postgresql-13-13.14/contrib/pageinspect/expected/hash.out --- postgresql-13-13.13/contrib/pageinspect/expected/hash.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pageinspect/expected/hash.out 2024-02-05 21:47:02.000000000 +0000 @@ -1,6 +1,8 @@ CREATE TABLE test_hash (a int, b text); INSERT INTO test_hash VALUES (1, 'one'); CREATE INDEX test_hash_a_idx ON test_hash USING hash (a); +CREATE TABLE test_hash_part (a int, b int) PARTITION BY RANGE (a); +CREATE INDEX test_hash_part_idx ON test_hash_part USING hash(b); \x SELECT hash_page_type(get_raw_page('test_hash_a_idx', 0)); -[ RECORD 1 ]--+--------- @@ -40,6 +42,8 @@ ERROR: invalid overflow block number 4 SELECT * FROM hash_bitmap_info('test_hash_a_idx', 5); ERROR: invalid overflow block number 5 +SELECT * FROM hash_bitmap_info('test_hash_part_idx', 1); -- error +ERROR: "test_hash_part_idx" is not a hash index SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, lowmask, ovflpoint, firstfree, nmaps, procid, spares, mapp FROM hash_metapage_info(get_raw_page('test_hash_a_idx', 0)); @@ -199,3 +203,4 @@ hash_page_type | unused DROP TABLE test_hash; +DROP TABLE test_hash_part; diff -Nru postgresql-13-13.13/contrib/pageinspect/hashfuncs.c postgresql-13-13.14/contrib/pageinspect/hashfuncs.c --- postgresql-13-13.13/contrib/pageinspect/hashfuncs.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pageinspect/hashfuncs.c 2024-02-05 21:47:02.000000000 +0000 @@ -12,6 +12,7 @@ #include "access/hash.h" #include "access/htup_details.h" +#include "access/relation.h" #include "catalog/pg_am.h" #include "catalog/pg_type.h" #include "funcapi.h" @@ -27,6 +28,7 @@ PG_FUNCTION_INFO_V1(hash_bitmap_info); PG_FUNCTION_INFO_V1(hash_metapage_info); +#define IS_INDEX(r) ((r)->rd_rel->relkind == RELKIND_INDEX) #define IS_HASH(r) ((r)->rd_rel->relam == HASH_AM_OID) /* ------------------------------------------------ @@ -417,9 +419,9 @@ (errcode(ERRCODE_INSUFFICIENT_PRIVILEGE), errmsg("must be superuser to use raw page functions"))); - indexRel = index_open(indexRelid, AccessShareLock); + indexRel = relation_open(indexRelid, AccessShareLock); - if (!IS_HASH(indexRel)) + if (!IS_INDEX(indexRel) || !IS_HASH(indexRel)) ereport(ERROR, (errcode(ERRCODE_WRONG_OBJECT_TYPE), errmsg("\"%s\" is not a %s index", diff -Nru postgresql-13-13.13/contrib/pageinspect/sql/hash.sql postgresql-13-13.14/contrib/pageinspect/sql/hash.sql --- postgresql-13-13.13/contrib/pageinspect/sql/hash.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pageinspect/sql/hash.sql 2024-02-05 21:47:02.000000000 +0000 @@ -2,6 +2,9 @@ INSERT INTO test_hash VALUES (1, 'one'); CREATE INDEX test_hash_a_idx ON test_hash USING hash (a); +CREATE TABLE test_hash_part (a int, b int) PARTITION BY RANGE (a); +CREATE INDEX test_hash_part_idx ON test_hash_part USING hash(b); + \x SELECT hash_page_type(get_raw_page('test_hash_a_idx', 0)); @@ -19,6 +22,7 @@ SELECT * FROM hash_bitmap_info('test_hash_a_idx', 3); SELECT * FROM hash_bitmap_info('test_hash_a_idx', 4); SELECT * FROM hash_bitmap_info('test_hash_a_idx', 5); +SELECT * FROM hash_bitmap_info('test_hash_part_idx', 1); -- error SELECT magic, version, ntuples, bsize, bmsize, bmshift, maxbucket, highmask, @@ -104,3 +108,4 @@ SELECT hash_page_type(decode(repeat('00', :block_size), 'hex')); DROP TABLE test_hash; +DROP TABLE test_hash_part; diff -Nru postgresql-13-13.13/contrib/pgcrypto/pgp-decrypt.c postgresql-13-13.14/contrib/pgcrypto/pgp-decrypt.c --- postgresql-13-13.13/contrib/pgcrypto/pgp-decrypt.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pgcrypto/pgp-decrypt.c 2024-02-05 21:47:02.000000000 +0000 @@ -250,7 +250,8 @@ uint8 tmpbuf[PGP_MAX_BLOCK + 2]; len = pgp_get_cipher_block_size(ctx->cipher_algo); - if (len > sizeof(tmpbuf)) + /* Make sure we have space for prefix */ + if (len > PGP_MAX_BLOCK) return PXE_BUG; res = pullf_read_max(src, len + 2, &buf, tmpbuf); diff -Nru postgresql-13-13.13/contrib/pgstattuple/expected/pgstattuple.out postgresql-13-13.14/contrib/pgstattuple/expected/pgstattuple.out --- postgresql-13-13.13/contrib/pgstattuple/expected/pgstattuple.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pgstattuple/expected/pgstattuple.out 2024-02-05 21:47:02.000000000 +0000 @@ -153,6 +153,7 @@ -- check that using any of these functions with unsupported relations will fail create table test_partitioned (a int) partition by range (a); create index test_partitioned_index on test_partitioned(a); +create index test_partitioned_hash_index on test_partitioned using hash(a); -- these should all fail select pgstattuple('test_partitioned'); ERROR: "test_partitioned" (partitioned table) is not supported @@ -167,7 +168,9 @@ select pgstatginindex('test_partitioned'); ERROR: relation "test_partitioned" is not a GIN index select pgstathashindex('test_partitioned'); -ERROR: "test_partitioned" is not an index +ERROR: relation "test_partitioned" is not a hash index +select pgstathashindex('test_partitioned_hash_index'); +ERROR: relation "test_partitioned_hash_index" is not a hash index create view test_view as select 1; -- these should all fail select pgstattuple('test_view'); @@ -181,7 +184,7 @@ select pgstatginindex('test_view'); ERROR: relation "test_view" is not a GIN index select pgstathashindex('test_view'); -ERROR: "test_view" is not an index +ERROR: relation "test_view" is not a hash index create foreign data wrapper dummy; create server dummy_server foreign data wrapper dummy; create foreign table test_foreign_table () server dummy_server; @@ -197,7 +200,7 @@ select pgstatginindex('test_foreign_table'); ERROR: relation "test_foreign_table" is not a GIN index select pgstathashindex('test_foreign_table'); -ERROR: "test_foreign_table" is not an index +ERROR: relation "test_foreign_table" is not a hash index -- a partition of a partitioned table should work though create table test_partition partition of test_partitioned for values from (1) to (100); select pgstattuple('test_partition'); @@ -224,7 +227,7 @@ select pgstatginindex('test_partition'); ERROR: relation "test_partition" is not a GIN index select pgstathashindex('test_partition'); -ERROR: "test_partition" is not an index +ERROR: relation "test_partition" is not a hash index -- an actual index of a partitioned table should work though create index test_partition_idx on test_partition(a); create index test_partition_hash_idx on test_partition using hash (a); diff -Nru postgresql-13-13.13/contrib/pgstattuple/pgstatindex.c postgresql-13-13.14/contrib/pgstattuple/pgstatindex.c --- postgresql-13-13.13/contrib/pgstattuple/pgstatindex.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pgstattuple/pgstatindex.c 2024-02-05 21:47:02.000000000 +0000 @@ -615,10 +615,9 @@ float8 free_percent; uint64 total_space; - rel = index_open(relid, AccessShareLock); + rel = relation_open(relid, AccessShareLock); - /* index_open() checks that it's an index */ - if (!IS_HASH(rel)) + if (!IS_INDEX(rel) || !IS_HASH(rel)) ereport(ERROR, (errcode(ERRCODE_WRONG_OBJECT_TYPE), errmsg("relation \"%s\" is not a hash index", diff -Nru postgresql-13-13.13/contrib/pgstattuple/sql/pgstattuple.sql postgresql-13-13.14/contrib/pgstattuple/sql/pgstattuple.sql --- postgresql-13-13.13/contrib/pgstattuple/sql/pgstattuple.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/pgstattuple/sql/pgstattuple.sql 2024-02-05 21:47:02.000000000 +0000 @@ -65,6 +65,7 @@ -- check that using any of these functions with unsupported relations will fail create table test_partitioned (a int) partition by range (a); create index test_partitioned_index on test_partitioned(a); +create index test_partitioned_hash_index on test_partitioned using hash(a); -- these should all fail select pgstattuple('test_partitioned'); select pgstattuple('test_partitioned_index'); @@ -73,6 +74,7 @@ select pgstatindex('test_partitioned'); select pgstatginindex('test_partitioned'); select pgstathashindex('test_partitioned'); +select pgstathashindex('test_partitioned_hash_index'); create view test_view as select 1; -- these should all fail diff -Nru postgresql-13-13.13/contrib/xml2/xpath.c postgresql-13-13.14/contrib/xml2/xpath.c --- postgresql-13-13.13/contrib/xml2/xpath.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/contrib/xml2/xpath.c 2024-02-05 21:47:02.000000000 +0000 @@ -75,7 +75,6 @@ xmlInitParser(); xmlSubstituteEntitiesDefault(1); - xmlLoadExtDtdDefaultValue = 1; return xmlerrcxt; } diff -Nru postgresql-13-13.13/debian/changelog postgresql-13-13.14/debian/changelog --- postgresql-13-13.13/debian/changelog 2023-11-07 13:45:51.000000000 +0000 +++ postgresql-13-13.14/debian/changelog 2024-02-06 12:54:51.000000000 +0000 @@ -1,3 +1,22 @@ +postgresql-13 (13.14-0+deb11u1) bullseye-security; urgency=medium + + * New upstream version. + + * Tighten security restrictions within REFRESH MATERIALIZED VIEW + CONCURRENTLY (Heikki Linnakangas) + + One step of a concurrent refresh command was run under weak security + restrictions. If a materialized view's owner could persuade a superuser + or other high-privileged user to perform a concurrent refresh on that + view, the view's owner could control code executed with the privileges + of the user running REFRESH. Fix things so that all user-determined code + is run as the view's owner, as expected. + + The PostgreSQL Project thanks Pedro Gallegos for reporting this problem. + (CVE-2024-0985) + + -- Christoph Berg Tue, 06 Feb 2024 13:54:51 +0100 + postgresql-13 (13.13-0+deb11u1) bullseye-security; urgency=medium * New upstream version. diff -Nru postgresql-13-13.13/doc/src/sgml/ddl.sgml postgresql-13-13.14/doc/src/sgml/ddl.sgml --- postgresql-13-13.13/doc/src/sgml/ddl.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/ddl.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1083,16 +1083,16 @@ A foreign key must reference columns that either are a primary key or - form a unique constraint. This means that the referenced columns always - have an index (the one underlying the primary key or unique constraint); - so checks on whether a referencing row has a match will be efficient. - Since a DELETE of a row from the referenced table - or an UPDATE of a referenced column will require - a scan of the referencing table for rows matching the old value, it - is often a good idea to index the referencing columns too. Because this - is not always needed, and there are many choices available on how - to index, declaration of a foreign key constraint does not - automatically create an index on the referencing columns. + form a unique constraint, or are columns from a non-partial unique index. + This means that the referenced columns always have an index to allow + efficient lookups on whether a referencing row has a match. Since a + DELETE of a row from the referenced table or an + UPDATE of a referenced column will require a scan of + the referencing table for rows matching the old value, it is often a good + idea to index the referencing columns too. Because this is not always + needed, and there are many choices available on how to index, the + declaration of a foreign key constraint does not automatically create an + index on the referencing columns. @@ -2140,9 +2140,16 @@ aclitem The privileges that have been granted for a particular object are - displayed as a list of aclitem entries, where each - aclitem describes the permissions of one grantee that - have been granted by a particular grantor. For example, + displayed as a list of aclitem entries, each having the + format: + +grantee=privilege-abbreviation*.../grantor + + Each aclitem lists all the permissions of one grantee that + have been granted by a particular grantor. Specific privileges are + represented by one-letter abbreviations from + , with * + appended if the privilege was granted with grant option. For example, calvin=r*w/hobbes specifies that the role calvin has the privilege SELECT (r) with grant option @@ -4026,7 +4033,7 @@ CREATE INDEX measurement_usls_idx ON ONLY measurement (unitsales); -CREATE INDEX measurement_usls_200602_idx +CREATE INDEX CONCURRENTLY measurement_usls_200602_idx ON measurement_y2006m02 (unitsales); ALTER INDEX measurement_usls_idx ATTACH PARTITION measurement_usls_200602_idx; @@ -4143,7 +4150,9 @@ Using ONLY to add or drop a constraint on only the partitioned table is supported as long as there are no partitions. Once partitions exist, using ONLY - will result in an error. Instead, constraints on the partitions + will result in an error for any constraints other than + UNIQUE and PRIMARY KEY. + Instead, constraints on the partitions themselves can be added and (if they are not present in the parent table) dropped. diff -Nru postgresql-13-13.13/doc/src/sgml/fdwhandler.sgml postgresql-13-13.14/doc/src/sgml/fdwhandler.sgml --- postgresql-13-13.13/doc/src/sgml/fdwhandler.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/fdwhandler.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -67,13 +67,16 @@ foreign tables using the wrapper. The validator function must be registered as taking two arguments, a text array containing the options to be validated, and an OID - representing the type of object the options are associated with (in - the form of the OID of the system catalog the object would be stored - in, either - ForeignDataWrapperRelationId, - ForeignServerRelationId, - UserMappingRelationId, - or ForeignTableRelationId). + representing the type of object the options are associated with. The + latter corresponds to the OID of the system catalog the object + would be stored in, one of: + + AttributeRelationId + ForeignDataWrapperRelationId + ForeignServerRelationId + ForeignTableRelationId + UserMappingRelationId + If no validator function is supplied, options are not checked at object creation time or object alteration time. diff -Nru postgresql-13-13.13/doc/src/sgml/high-availability.sgml postgresql-13-13.14/doc/src/sgml/high-availability.sgml --- postgresql-13-13.13/doc/src/sgml/high-availability.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/high-availability.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -650,7 +650,7 @@ later disconnected, the standby goes back to step 1 and tries to restore the file from the archive again. This loop of retries from the archive, pg_wal, and via streaming replication goes on until the server - is stopped or failover is triggered by a trigger file. + is stopped or is promoted. diff -Nru postgresql-13-13.13/doc/src/sgml/html/acronyms.html postgresql-13-13.14/doc/src/sgml/html/acronyms.html --- postgresql-13-13.13/doc/src/sgml/html/acronyms.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/acronyms.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/admin.html postgresql-13-13.14/doc/src/sgml/html/admin.html --- postgresql-13-13.13/doc/src/sgml/html/admin.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/admin.html 2024-02-05 22:04:12.000000000 +0000 @@ -1,5 +1,5 @@ -Part III. Server Administration
Part III. Server Administration
Prev UpPostgreSQL 13.13 DocumentationHome Next

Part III. Server Administration

+Part III. Server Administration

Part III. Server Administration
Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/adminpack.html postgresql-13-13.14/doc/src/sgml/html/adminpack.html --- postgresql-13-13.13/doc/src/sgml/html/adminpack.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/adminpack.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/amcheck.html postgresql-13-13.14/doc/src/sgml/html/amcheck.html --- postgresql-13-13.13/doc/src/sgml/html/amcheck.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/amcheck.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/app-clusterdb.html postgresql-13-13.14/doc/src/sgml/html/app-clusterdb.html --- postgresql-13-13.13/doc/src/sgml/html/app-clusterdb.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-clusterdb.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/app-createdb.html postgresql-13-13.14/doc/src/sgml/html/app-createdb.html --- postgresql-13-13.13/doc/src/sgml/html/app-createdb.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-createdb.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/app-createuser.html postgresql-13-13.14/doc/src/sgml/html/app-createuser.html --- postgresql-13-13.13/doc/src/sgml/html/app-createuser.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-createuser.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/app-dropdb.html postgresql-13-13.14/doc/src/sgml/html/app-dropdb.html --- postgresql-13-13.13/doc/src/sgml/html/app-dropdb.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-dropdb.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-dropuser.html postgresql-13-13.14/doc/src/sgml/html/app-dropuser.html --- postgresql-13-13.13/doc/src/sgml/html/app-dropuser.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-dropuser.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-ecpg.html postgresql-13-13.14/doc/src/sgml/html/app-ecpg.html --- postgresql-13-13.13/doc/src/sgml/html/app-ecpg.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-ecpg.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-initdb.html postgresql-13-13.14/doc/src/sgml/html/app-initdb.html --- postgresql-13-13.13/doc/src/sgml/html/app-initdb.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-initdb.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-pg-ctl.html postgresql-13-13.14/doc/src/sgml/html/app-pg-ctl.html --- postgresql-13-13.13/doc/src/sgml/html/app-pg-ctl.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pg-ctl.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-pg-dumpall.html postgresql-13-13.14/doc/src/sgml/html/app-pg-dumpall.html --- postgresql-13-13.13/doc/src/sgml/html/app-pg-dumpall.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pg-dumpall.html 2024-02-05 22:04:24.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 @@ -352,4 +352,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.13/doc/src/sgml/html/app-pg-isready.html postgresql-13-13.14/doc/src/sgml/html/app-pg-isready.html --- postgresql-13-13.13/doc/src/sgml/html/app-pg-isready.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pg-isready.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-pgbasebackup.html postgresql-13-13.14/doc/src/sgml/html/app-pgbasebackup.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgbasebackup.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgbasebackup.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-pgchecksums.html postgresql-13-13.14/doc/src/sgml/html/app-pgchecksums.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgchecksums.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgchecksums.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-pgconfig.html postgresql-13-13.14/doc/src/sgml/html/app-pgconfig.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgconfig.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgconfig.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-pgcontroldata.html postgresql-13-13.14/doc/src/sgml/html/app-pgcontroldata.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgcontroldata.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgcontroldata.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-pgdump.html postgresql-13-13.14/doc/src/sgml/html/app-pgdump.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgdump.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgdump.html 2024-02-05 22:04:24.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 @@ -798,4 +798,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.13/doc/src/sgml/html/app-pgreceivewal.html postgresql-13-13.14/doc/src/sgml/html/app-pgreceivewal.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgreceivewal.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgreceivewal.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-pgreceivexlog.html postgresql-13-13.14/doc/src/sgml/html/app-pgreceivexlog.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgreceivexlog.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgreceivexlog.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/app-pgrecvlogical.html postgresql-13-13.14/doc/src/sgml/html/app-pgrecvlogical.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgrecvlogical.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgrecvlogical.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-pgresetwal.html postgresql-13-13.14/doc/src/sgml/html/app-pgresetwal.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgresetwal.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgresetwal.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-pgresetxlog.html postgresql-13-13.14/doc/src/sgml/html/app-pgresetxlog.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgresetxlog.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgresetxlog.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/app-pgrestore.html postgresql-13-13.14/doc/src/sgml/html/app-pgrestore.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgrestore.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgrestore.html 2024-02-05 22:04:24.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

@@ -492,4 +492,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.13/doc/src/sgml/html/app-pgrewind.html postgresql-13-13.14/doc/src/sgml/html/app-pgrewind.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgrewind.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgrewind.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-pgverifybackup.html postgresql-13-13.14/doc/src/sgml/html/app-pgverifybackup.html --- postgresql-13-13.13/doc/src/sgml/html/app-pgverifybackup.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-pgverifybackup.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/app-postgres.html postgresql-13-13.14/doc/src/sgml/html/app-postgres.html --- postgresql-13-13.13/doc/src/sgml/html/app-postgres.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-postgres.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-postmaster.html postgresql-13-13.14/doc/src/sgml/html/app-postmaster.html --- postgresql-13-13.13/doc/src/sgml/html/app-postmaster.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-postmaster.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-psql.html postgresql-13-13.14/doc/src/sgml/html/app-psql.html --- postgresql-13-13.13/doc/src/sgml/html/app-psql.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-psql.html 2024-02-05 22:04:25.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.13)
+psql (13.14)
 Type "help" for help.
 
 testdb=>
@@ -2819,4 +2819,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.13/doc/src/sgml/html/app-reindexdb.html postgresql-13-13.14/doc/src/sgml/html/app-reindexdb.html --- postgresql-13-13.13/doc/src/sgml/html/app-reindexdb.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-reindexdb.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/app-vacuumdb.html postgresql-13-13.14/doc/src/sgml/html/app-vacuumdb.html --- postgresql-13-13.13/doc/src/sgml/html/app-vacuumdb.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/app-vacuumdb.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/appendix-obsolete.html postgresql-13-13.14/doc/src/sgml/html/appendix-obsolete.html --- postgresql-13-13.13/doc/src/sgml/html/appendix-obsolete.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/appendix-obsolete.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/appendixes.html postgresql-13-13.14/doc/src/sgml/html/appendixes.html --- postgresql-13-13.13/doc/src/sgml/html/appendixes.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/appendixes.html 2024-02-05 22:04:34.000000000 +0000 @@ -1,2 +1,2 @@ -Part VIII. Appendixes
Part VIII. Appendixes
Prev UpPostgreSQL 13.13 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.13
E.2. Release 13.12
E.3. Release 13.11
E.4. Release 13.10
E.5. Release 13.9
E.6. Release 13.8
E.7. Release 13.7
E.8. Release 13.6
E.9. Release 13.5
E.10. Release 13.4
E.11. Release 13.3
E.12. Release 13.2
E.13. Release 13.1
E.14. Release 13
E.15. 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.14 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.14
E.2. Release 13.13
E.3. Release 13.12
E.4. Release 13.11
E.5. Release 13.10
E.6. Release 13.9
E.7. Release 13.8
E.8. Release 13.7
E.9. Release 13.6
E.10. Release 13.5
E.11. Release 13.4
E.12. Release 13.3
E.13. Release 13.2
E.14. Release 13.1
E.15. Release 13
E.16. 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.13/doc/src/sgml/html/applevel-consistency.html postgresql-13-13.14/doc/src/sgml/html/applevel-consistency.html --- postgresql-13-13.13/doc/src/sgml/html/applevel-consistency.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/applevel-consistency.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/arrays.html postgresql-13-13.14/doc/src/sgml/html/arrays.html --- postgresql-13-13.13/doc/src/sgml/html/arrays.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/arrays.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/auth-bsd.html postgresql-13-13.14/doc/src/sgml/html/auth-bsd.html --- postgresql-13-13.13/doc/src/sgml/html/auth-bsd.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-bsd.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-cert.html postgresql-13-13.14/doc/src/sgml/html/auth-cert.html --- postgresql-13-13.13/doc/src/sgml/html/auth-cert.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-cert.html 2024-02-05 22:04:10.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; see Section 18.9.2 for SSL configuration instructions. @@ -22,4 +22,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.13/doc/src/sgml/html/auth-delay.html postgresql-13-13.14/doc/src/sgml/html/auth-delay.html --- postgresql-13-13.13/doc/src/sgml/html/auth-delay.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-delay.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/auth-ident.html postgresql-13-13.14/doc/src/sgml/html/auth-ident.html --- postgresql-13-13.13/doc/src/sgml/html/auth-ident.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-ident.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-ldap.html postgresql-13-13.14/doc/src/sgml/html/auth-ldap.html --- postgresql-13-13.13/doc/src/sgml/html/auth-ldap.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-ldap.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-methods.html postgresql-13-13.14/doc/src/sgml/html/auth-methods.html --- postgresql-13-13.13/doc/src/sgml/html/auth-methods.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-methods.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-pam.html postgresql-13-13.14/doc/src/sgml/html/auth-pam.html --- postgresql-13-13.13/doc/src/sgml/html/auth-pam.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-pam.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-password.html postgresql-13-13.14/doc/src/sgml/html/auth-password.html --- postgresql-13-13.13/doc/src/sgml/html/auth-password.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-password.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-peer.html postgresql-13-13.14/doc/src/sgml/html/auth-peer.html --- postgresql-13-13.13/doc/src/sgml/html/auth-peer.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-peer.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-pg-hba-conf.html postgresql-13-13.14/doc/src/sgml/html/auth-pg-hba-conf.html --- postgresql-13-13.13/doc/src/sgml/html/auth-pg-hba-conf.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-pg-hba-conf.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-radius.html postgresql-13-13.14/doc/src/sgml/html/auth-radius.html --- postgresql-13-13.13/doc/src/sgml/html/auth-radius.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-radius.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-trust.html postgresql-13-13.14/doc/src/sgml/html/auth-trust.html --- postgresql-13-13.13/doc/src/sgml/html/auth-trust.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-trust.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auth-username-maps.html postgresql-13-13.14/doc/src/sgml/html/auth-username-maps.html --- postgresql-13-13.13/doc/src/sgml/html/auth-username-maps.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auth-username-maps.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/auto-explain.html postgresql-13-13.14/doc/src/sgml/html/auto-explain.html --- postgresql-13-13.13/doc/src/sgml/html/auto-explain.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/auto-explain.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/backup-dump.html postgresql-13-13.14/doc/src/sgml/html/backup-dump.html --- postgresql-13-13.13/doc/src/sgml/html/backup-dump.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup-dump.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/backup-file.html postgresql-13-13.14/doc/src/sgml/html/backup-file.html --- postgresql-13-13.13/doc/src/sgml/html/backup-file.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup-file.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/backup-manifest-files.html postgresql-13-13.14/doc/src/sgml/html/backup-manifest-files.html --- postgresql-13-13.13/doc/src/sgml/html/backup-manifest-files.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup-manifest-files.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/backup-manifest-format.html postgresql-13-13.14/doc/src/sgml/html/backup-manifest-format.html --- postgresql-13-13.13/doc/src/sgml/html/backup-manifest-format.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup-manifest-format.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/backup-manifest-toplevel.html postgresql-13-13.14/doc/src/sgml/html/backup-manifest-toplevel.html --- postgresql-13-13.13/doc/src/sgml/html/backup-manifest-toplevel.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup-manifest-toplevel.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/backup-manifest-wal-ranges.html postgresql-13-13.14/doc/src/sgml/html/backup-manifest-wal-ranges.html --- postgresql-13-13.13/doc/src/sgml/html/backup-manifest-wal-ranges.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup-manifest-wal-ranges.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/backup.html postgresql-13-13.14/doc/src/sgml/html/backup.html --- postgresql-13-13.13/doc/src/sgml/html/backup.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/backup.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/bgworker.html postgresql-13-13.14/doc/src/sgml/html/bgworker.html --- postgresql-13-13.13/doc/src/sgml/html/bgworker.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bgworker.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/biblio.html postgresql-13-13.14/doc/src/sgml/html/biblio.html --- postgresql-13-13.13/doc/src/sgml/html/biblio.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/biblio.html 2024-02-05 22:04:34.000000000 +0000 @@ -1,5 +1,5 @@ -Bibliography
Bibliography
Prev UpPostgreSQL 13.13 DocumentationHome Next

Bibliography

+Bibliography

Bibliography
Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/bki-commands.html postgresql-13-13.14/doc/src/sgml/html/bki-commands.html --- postgresql-13-13.13/doc/src/sgml/html/bki-commands.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bki-commands.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/bki-example.html postgresql-13-13.14/doc/src/sgml/html/bki-example.html --- postgresql-13-13.13/doc/src/sgml/html/bki-example.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bki-example.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/bki-format.html postgresql-13-13.14/doc/src/sgml/html/bki-format.html --- postgresql-13-13.13/doc/src/sgml/html/bki-format.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bki-format.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/bki-structure.html postgresql-13-13.14/doc/src/sgml/html/bki-structure.html --- postgresql-13-13.13/doc/src/sgml/html/bki-structure.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bki-structure.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/bki.html postgresql-13-13.14/doc/src/sgml/html/bki.html --- postgresql-13-13.13/doc/src/sgml/html/bki.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bki.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/bloom.html postgresql-13-13.14/doc/src/sgml/html/bloom.html --- postgresql-13-13.13/doc/src/sgml/html/bloom.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bloom.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/bookindex.html postgresql-13-13.14/doc/src/sgml/html/bookindex.html --- postgresql-13-13.13/doc/src/sgml/html/bookindex.html 2023-11-06 22:30:57.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bookindex.html 2024-02-05 22:04:36.000000000 +0000 @@ -1,5 +1,5 @@ -Index
Index
Prev UpPostgreSQL 13.13 DocumentationHome 

Index

Symbols +Index

Index
Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/brin-builtin-opclasses.html postgresql-13-13.14/doc/src/sgml/html/brin-builtin-opclasses.html --- postgresql-13-13.13/doc/src/sgml/html/brin-builtin-opclasses.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/brin-builtin-opclasses.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/brin-extensibility.html postgresql-13-13.14/doc/src/sgml/html/brin-extensibility.html --- postgresql-13-13.13/doc/src/sgml/html/brin-extensibility.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/brin-extensibility.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/brin-intro.html postgresql-13-13.14/doc/src/sgml/html/brin-intro.html --- postgresql-13-13.13/doc/src/sgml/html/brin-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/brin-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/brin.html postgresql-13-13.14/doc/src/sgml/html/brin.html --- postgresql-13-13.13/doc/src/sgml/html/brin.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/brin.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/btree-behavior.html postgresql-13-13.14/doc/src/sgml/html/btree-behavior.html --- postgresql-13-13.13/doc/src/sgml/html/btree-behavior.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree-behavior.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/btree-gin.html postgresql-13-13.14/doc/src/sgml/html/btree-gin.html --- postgresql-13-13.13/doc/src/sgml/html/btree-gin.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree-gin.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/btree-gist.html postgresql-13-13.14/doc/src/sgml/html/btree-gist.html --- postgresql-13-13.13/doc/src/sgml/html/btree-gist.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree-gist.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/btree-implementation.html postgresql-13-13.14/doc/src/sgml/html/btree-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/btree-implementation.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree-implementation.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/btree-intro.html postgresql-13-13.14/doc/src/sgml/html/btree-intro.html --- postgresql-13-13.13/doc/src/sgml/html/btree-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/btree-support-funcs.html postgresql-13-13.14/doc/src/sgml/html/btree-support-funcs.html --- postgresql-13-13.13/doc/src/sgml/html/btree-support-funcs.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree-support-funcs.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/btree.html postgresql-13-13.14/doc/src/sgml/html/btree.html --- postgresql-13-13.13/doc/src/sgml/html/btree.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/btree.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/bug-reporting.html postgresql-13-13.14/doc/src/sgml/html/bug-reporting.html --- postgresql-13-13.13/doc/src/sgml/html/bug-reporting.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/bug-reporting.html 2024-02-05 22:04:04.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.13 we will almost certainly + If your version is older than 13.14 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.13/doc/src/sgml/html/catalog-pg-aggregate.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-aggregate.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-aggregate.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-aggregate.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/catalog-pg-am.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-am.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-am.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-am.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/catalog-pg-amop.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-amop.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-amop.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-amop.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/catalog-pg-amproc.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-amproc.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-amproc.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-amproc.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/catalog-pg-attrdef.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-attrdef.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-attrdef.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-attrdef.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-attribute.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-attribute.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-attribute.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-attribute.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-auth-members.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-auth-members.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-auth-members.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-auth-members.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-authid.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-authid.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-authid.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-authid.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-cast.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-cast.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-cast.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-cast.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-class.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-class.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-class.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-class.html 2024-02-05 22:04:26.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 describes tables and other objects that have columns or are 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.13/doc/src/sgml/html/catalog-pg-collation.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-collation.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-collation.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-collation.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-constraint.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-constraint.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-constraint.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-constraint.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-conversion.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-conversion.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-conversion.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-conversion.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-database.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-database.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-database.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-database.html 2024-02-05 22:04:26.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 @@ -109,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.13/doc/src/sgml/html/catalog-pg-db-role-setting.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-db-role-setting.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-db-role-setting.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-db-role-setting.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-default-acl.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-default-acl.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-default-acl.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-default-acl.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-depend.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-depend.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-depend.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-depend.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-description.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-description.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-description.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-description.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-enum.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-enum.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-enum.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-enum.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-event-trigger.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-event-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-event-trigger.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-event-trigger.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-extension.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-extension.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-extension.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-extension.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-foreign-data-wrapper.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-foreign-server.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-foreign-server.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-foreign-server.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-foreign-server.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-foreign-table.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-foreign-table.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-foreign-table.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-foreign-table.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-index.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-index.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-index.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-index.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-inherits.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-inherits.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-inherits.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-inherits.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-init-privs.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-init-privs.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-init-privs.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-init-privs.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-language.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-language.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-language.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-language.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-largeobject-metadata.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-largeobject-metadata.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-largeobject-metadata.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-largeobject.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-largeobject.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-largeobject.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-largeobject.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-namespace.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-namespace.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-namespace.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-namespace.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-opclass.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-opclass.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-opclass.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-opclass.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-operator.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-operator.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-operator.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-operator.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-opfamily.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-opfamily.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-opfamily.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-opfamily.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-partitioned-table.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-partitioned-table.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-partitioned-table.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-partitioned-table.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-policy.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-policy.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-policy.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-policy.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-proc.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-proc.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-proc.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-proc.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-publication-rel.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-publication-rel.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-publication-rel.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-publication-rel.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-publication.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-publication.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-publication.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-publication.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-range.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-range.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-range.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-range.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-replication-origin.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-replication-origin.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-replication-origin.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-replication-origin.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-rewrite.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-rewrite.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-rewrite.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-rewrite.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-seclabel.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-seclabel.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-seclabel.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-seclabel.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-sequence.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-sequence.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-sequence.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-sequence.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-shdepend.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-shdepend.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-shdepend.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-shdepend.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-shdescription.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-shdescription.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-shdescription.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-shdescription.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-shseclabel.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-shseclabel.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-shseclabel.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-shseclabel.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-statistic-ext-data.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-statistic-ext-data.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-statistic-ext-data.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-statistic-ext-data.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-statistic-ext.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-statistic-ext.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-statistic-ext.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-statistic-ext.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-statistic.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-statistic.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-statistic.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-statistic.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-subscription-rel.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-subscription-rel.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-subscription-rel.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-subscription-rel.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-subscription.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-subscription.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-subscription.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-subscription.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-tablespace.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-tablespace.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-tablespace.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-tablespace.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-transform.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-transform.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-transform.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-transform.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-trigger.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-trigger.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-trigger.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-ts-config-map.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-config-map.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-ts-config-map.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-config-map.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-ts-config.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-config.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-ts-config.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-config.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-ts-dict.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-dict.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-ts-dict.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-dict.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-ts-parser.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-parser.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-ts-parser.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-parser.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-ts-template.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-template.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-ts-template.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-ts-template.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-type.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-type.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-type.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-type.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalog-pg-user-mapping.html postgresql-13-13.14/doc/src/sgml/html/catalog-pg-user-mapping.html --- postgresql-13-13.13/doc/src/sgml/html/catalog-pg-user-mapping.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalog-pg-user-mapping.html 2024-02-05 22:04:26.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.13/doc/src/sgml/html/catalogs-overview.html postgresql-13-13.14/doc/src/sgml/html/catalogs-overview.html --- postgresql-13-13.13/doc/src/sgml/html/catalogs-overview.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalogs-overview.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/catalogs.html postgresql-13-13.14/doc/src/sgml/html/catalogs.html --- postgresql-13-13.13/doc/src/sgml/html/catalogs.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/catalogs.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/charset.html postgresql-13-13.14/doc/src/sgml/html/charset.html --- postgresql-13-13.13/doc/src/sgml/html/charset.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/charset.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/citext.html postgresql-13-13.14/doc/src/sgml/html/citext.html --- postgresql-13-13.13/doc/src/sgml/html/citext.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/citext.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/client-authentication-problems.html postgresql-13-13.14/doc/src/sgml/html/client-authentication-problems.html --- postgresql-13-13.13/doc/src/sgml/html/client-authentication-problems.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/client-authentication-problems.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/client-authentication.html postgresql-13-13.14/doc/src/sgml/html/client-authentication.html --- postgresql-13-13.13/doc/src/sgml/html/client-authentication.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/client-authentication.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/client-interfaces.html postgresql-13-13.14/doc/src/sgml/html/client-interfaces.html --- postgresql-13-13.13/doc/src/sgml/html/client-interfaces.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/client-interfaces.html 2024-02-05 22:04:14.000000000 +0000 @@ -1,5 +1,5 @@ -Part IV. Client Interfaces
Part IV. Client Interfaces
Prev UpPostgreSQL 13.13 DocumentationHome Next

Part IV. Client Interfaces

+Part IV. Client Interfaces

Part IV. Client Interfaces
Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/collation.html postgresql-13-13.14/doc/src/sgml/html/collation.html --- postgresql-13-13.13/doc/src/sgml/html/collation.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/collation.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/color-when.html postgresql-13-13.14/doc/src/sgml/html/color-when.html --- postgresql-13-13.13/doc/src/sgml/html/color-when.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/color-when.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/color-which.html postgresql-13-13.14/doc/src/sgml/html/color-which.html --- postgresql-13-13.13/doc/src/sgml/html/color-which.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/color-which.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/color.html postgresql-13-13.14/doc/src/sgml/html/color.html --- postgresql-13-13.13/doc/src/sgml/html/color.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/color.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/config-setting.html postgresql-13-13.14/doc/src/sgml/html/config-setting.html --- postgresql-13-13.13/doc/src/sgml/html/config-setting.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/config-setting.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/connect-estab.html postgresql-13-13.14/doc/src/sgml/html/connect-estab.html --- postgresql-13-13.13/doc/src/sgml/html/connect-estab.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/connect-estab.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/continuous-archiving.html postgresql-13-13.14/doc/src/sgml/html/continuous-archiving.html --- postgresql-13-13.13/doc/src/sgml/html/continuous-archiving.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/continuous-archiving.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/contrib-dblink-build-sql-delete.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-build-sql-delete.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-build-sql-delete.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-build-sql-insert.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-build-sql-insert.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-build-sql-insert.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-build-sql-insert.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-build-sql-update.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-build-sql-update.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-build-sql-update.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-build-sql-update.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-cancel-query.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-cancel-query.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-cancel-query.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-cancel-query.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-close.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-close.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-close.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-close.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-connect-u.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-connect-u.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-connect-u.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-connect-u.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-connect.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-connect.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-connect.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-connect.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-disconnect.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-disconnect.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-disconnect.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-disconnect.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-error-message.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-error-message.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-error-message.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-error-message.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-exec.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-exec.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-exec.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-exec.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-fetch.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-fetch.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-fetch.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-fetch.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-function.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-function.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-function.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-function.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-get-connections.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-connections.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-get-connections.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-connections.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-get-notify.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-notify.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-get-notify.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-notify.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-get-pkey.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-pkey.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-get-pkey.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-pkey.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-get-result.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-result.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-get-result.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-get-result.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-is-busy.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-is-busy.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-is-busy.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-is-busy.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-open.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-open.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-open.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-open.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-dblink-send-query.html postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-send-query.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-dblink-send-query.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-dblink-send-query.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/contrib-prog-client.html postgresql-13-13.14/doc/src/sgml/html/contrib-prog-client.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-prog-client.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-prog-client.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/contrib-prog-server.html postgresql-13-13.14/doc/src/sgml/html/contrib-prog-server.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-prog-server.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-prog-server.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/contrib-prog.html postgresql-13-13.14/doc/src/sgml/html/contrib-prog.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-prog.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-prog.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/contrib-spi.html postgresql-13-13.14/doc/src/sgml/html/contrib-spi.html --- postgresql-13-13.13/doc/src/sgml/html/contrib-spi.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib-spi.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/contrib.html postgresql-13-13.14/doc/src/sgml/html/contrib.html --- postgresql-13-13.13/doc/src/sgml/html/contrib.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/contrib.html 2024-02-05 22:04:33.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.15. Prior Releases Home F.1. adminpack
    \ No newline at end of file +

    Prev Up Next
    E.16. Prior Releases Home F.1. adminpack
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/creating-cluster.html postgresql-13-13.14/doc/src/sgml/html/creating-cluster.html --- postgresql-13-13.13/doc/src/sgml/html/creating-cluster.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/creating-cluster.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/cube.html postgresql-13-13.14/doc/src/sgml/html/cube.html --- postgresql-13-13.13/doc/src/sgml/html/cube.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/cube.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/custom-scan-execution.html postgresql-13-13.14/doc/src/sgml/html/custom-scan-execution.html --- postgresql-13-13.13/doc/src/sgml/html/custom-scan-execution.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/custom-scan-execution.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/custom-scan-path.html postgresql-13-13.14/doc/src/sgml/html/custom-scan-path.html --- postgresql-13-13.13/doc/src/sgml/html/custom-scan-path.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/custom-scan-path.html 2024-02-05 22:04:28.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 @@ -91,4 +91,4 @@ 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 +

    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.13/doc/src/sgml/html/custom-scan-plan.html postgresql-13-13.14/doc/src/sgml/html/custom-scan-plan.html --- postgresql-13-13.13/doc/src/sgml/html/custom-scan-plan.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/custom-scan-plan.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/custom-scan.html postgresql-13-13.14/doc/src/sgml/html/custom-scan.html --- postgresql-13-13.13/doc/src/sgml/html/custom-scan.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/custom-scan.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/database-roles.html postgresql-13-13.14/doc/src/sgml/html/database-roles.html --- postgresql-13-13.13/doc/src/sgml/html/database-roles.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/database-roles.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/datatype-binary.html postgresql-13-13.14/doc/src/sgml/html/datatype-binary.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-binary.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-binary.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-bit.html postgresql-13-13.14/doc/src/sgml/html/datatype-bit.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-bit.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-bit.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-boolean.html postgresql-13-13.14/doc/src/sgml/html/datatype-boolean.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-boolean.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-boolean.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-character.html postgresql-13-13.14/doc/src/sgml/html/datatype-character.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-character.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-character.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-datetime.html postgresql-13-13.14/doc/src/sgml/html/datatype-datetime.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-datetime.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-datetime.html 2024-02-05 22:04:05.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 @@ -546,4 +546,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.13/doc/src/sgml/html/datatype-enum.html postgresql-13-13.14/doc/src/sgml/html/datatype-enum.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-enum.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-enum.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-geometric.html postgresql-13-13.14/doc/src/sgml/html/datatype-geometric.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-geometric.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-geometric.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-json.html postgresql-13-13.14/doc/src/sgml/html/datatype-json.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-json.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-json.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-money.html postgresql-13-13.14/doc/src/sgml/html/datatype-money.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-money.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-money.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-net-types.html postgresql-13-13.14/doc/src/sgml/html/datatype-net-types.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-net-types.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-net-types.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-numeric.html postgresql-13-13.14/doc/src/sgml/html/datatype-numeric.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-numeric.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-numeric.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-oid.html postgresql-13-13.14/doc/src/sgml/html/datatype-oid.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-oid.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-oid.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/datatype-pg-lsn.html postgresql-13-13.14/doc/src/sgml/html/datatype-pg-lsn.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-pg-lsn.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-pg-lsn.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/datatype-pseudo.html postgresql-13-13.14/doc/src/sgml/html/datatype-pseudo.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-pseudo.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-pseudo.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/datatype-textsearch.html postgresql-13-13.14/doc/src/sgml/html/datatype-textsearch.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-textsearch.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-textsearch.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-uuid.html postgresql-13-13.14/doc/src/sgml/html/datatype-uuid.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-uuid.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-uuid.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype-xml.html postgresql-13-13.14/doc/src/sgml/html/datatype-xml.html --- postgresql-13-13.13/doc/src/sgml/html/datatype-xml.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype-xml.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/datatype.html postgresql-13-13.14/doc/src/sgml/html/datatype.html --- postgresql-13-13.13/doc/src/sgml/html/datatype.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datatype.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/datetime-appendix.html postgresql-13-13.14/doc/src/sgml/html/datetime-appendix.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-appendix.html 2023-11-06 22:30:51.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-appendix.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-config-files.html postgresql-13-13.14/doc/src/sgml/html/datetime-config-files.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-config-files.html 2023-11-06 22:30:51.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-config-files.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-input-rules.html postgresql-13-13.14/doc/src/sgml/html/datetime-input-rules.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-input-rules.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-input-rules.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-invalid-input.html postgresql-13-13.14/doc/src/sgml/html/datetime-invalid-input.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-invalid-input.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-invalid-input.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-julian-dates.html postgresql-13-13.14/doc/src/sgml/html/datetime-julian-dates.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-julian-dates.html 2023-11-06 22:30:51.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-julian-dates.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-keywords.html postgresql-13-13.14/doc/src/sgml/html/datetime-keywords.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-keywords.html 2023-11-06 22:30:51.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-keywords.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-posix-timezone-specs.html postgresql-13-13.14/doc/src/sgml/html/datetime-posix-timezone-specs.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-posix-timezone-specs.html 2023-11-06 22:30:51.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-posix-timezone-specs.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/datetime-units-history.html postgresql-13-13.14/doc/src/sgml/html/datetime-units-history.html --- postgresql-13-13.13/doc/src/sgml/html/datetime-units-history.html 2023-11-06 22:30:51.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/datetime-units-history.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/dblink.html postgresql-13-13.14/doc/src/sgml/html/dblink.html --- postgresql-13-13.13/doc/src/sgml/html/dblink.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dblink.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/ddl-basics.html postgresql-13-13.14/doc/src/sgml/html/ddl-basics.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-basics.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-basics.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/ddl-constraints.html postgresql-13-13.14/doc/src/sgml/html/ddl-constraints.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-constraints.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-constraints.html 2024-02-05 22:04:04.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 @@ -506,16 +506,16 @@ referencing column(s) as NOT NULL.

    A foreign key must reference columns that either are a primary key or - form a unique constraint. This means that the referenced columns always - have an index (the one underlying the primary key or unique constraint); - so checks on whether a referencing row has a match will be efficient. - Since a DELETE of a row from the referenced table - or an UPDATE of a referenced column will require - a scan of the referencing table for rows matching the old value, it - is often a good idea to index the referencing columns too. Because this - is not always needed, and there are many choices available on how - to index, declaration of a foreign key constraint does not - automatically create an index on the referencing columns. + form a unique constraint, or are columns from a non-partial unique index. + This means that the referenced columns always have an index to allow + efficient lookups on whether a referencing row has a match. Since a + DELETE of a row from the referenced table or an + UPDATE of a referenced column will require a scan of + the referencing table for rows matching the old value, it is often a good + idea to index the referencing columns too. Because this is not always + needed, and there are many choices available on how to index, the + declaration of a foreign key constraint does not automatically create an + index on the referencing columns.

    More information about updating and deleting data is in Chapter 6. Also see the description of foreign key constraint syntax in the reference documentation for @@ -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.13/doc/src/sgml/html/ddl-default.html postgresql-13-13.14/doc/src/sgml/html/ddl-default.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-default.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-default.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/ddl-depend.html postgresql-13-13.14/doc/src/sgml/html/ddl-depend.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-depend.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-depend.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/ddl-foreign-data.html postgresql-13-13.14/doc/src/sgml/html/ddl-foreign-data.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-foreign-data.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-foreign-data.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/ddl-generated-columns.html postgresql-13-13.14/doc/src/sgml/html/ddl-generated-columns.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-generated-columns.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-generated-columns.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/ddl-inherit.html postgresql-13-13.14/doc/src/sgml/html/ddl-inherit.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-inherit.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-inherit.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/ddl-others.html postgresql-13-13.14/doc/src/sgml/html/ddl-others.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-others.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-others.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/ddl-partitioning.html postgresql-13-13.14/doc/src/sgml/html/ddl-partitioning.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-partitioning.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-partitioning.html 2024-02-05 22:04:05.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. @@ -358,7 +358,7 @@ 

     CREATE INDEX measurement_usls_idx ON ONLY measurement (unitsales);
 
-CREATE INDEX measurement_usls_200602_idx
+CREATE INDEX CONCURRENTLY measurement_usls_200602_idx
     ON measurement_y2006m02 (unitsales);
 ALTER INDEX measurement_usls_idx
     ATTACH PARTITION measurement_usls_200602_idx;
@@ -439,7 +439,9 @@
         Using ONLY to add or drop a constraint on only
         the partitioned table is supported as long as there are no
         partitions.  Once partitions exist, using ONLY
-        will result in an error.  Instead, constraints on the partitions
+        will result in an error for any constraints other than
+        UNIQUE and PRIMARY KEY.
+        Instead, constraints on the partitions
         themselves can be added and (if they are not present in the parent
         table) dropped.
        
  • 
@@ -993,4 +995,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.13/doc/src/sgml/html/ddl-priv.html postgresql-13-13.14/doc/src/sgml/html/ddl-priv.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-priv.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-priv.html 2024-02-05 22:04:05.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 @@ -238,9 +238,16 @@

    Table 5.2. Summary of Access Privileges

    Object TypeAll PrivilegesDefault PUBLIC Privilegespsql Command
    DATABASECTcTc\l
    DOMAINUU\dD+
    FUNCTION or PROCEDUREXX\df+
    FOREIGN DATA WRAPPERUnone\dew+
    FOREIGN SERVERUnone\des+
    LANGUAGEUU\dL+
    LARGE OBJECTrwnone 
    SCHEMAUCnone\dn+
    SEQUENCErwUnone\dp
    TABLE (and table-like objects)arwdDxtnone\dp
    Table columnarwxnone\dp
    TABLESPACECnone\db+
    TYPEUU\dT+

    The privileges that have been granted for a particular object are - displayed as a list of aclitem entries, where each - aclitem describes the permissions of one grantee that - have been granted by a particular grantor. For example, + displayed as a list of aclitem entries, each having the + format: +

    +grantee=privilege-abbreviation[*].../grantor
+

    + Each aclitem lists all the permissions of one grantee that + have been granted by a particular grantor. Specific privileges are + represented by one-letter abbreviations from + Table 5.1, with * + appended if the privilege was granted with grant option. For example, calvin=r*w/hobbes specifies that the role calvin has the privilege SELECT (r) with grant option @@ -293,4 +300,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.13/doc/src/sgml/html/ddl-rowsecurity.html postgresql-13-13.14/doc/src/sgml/html/ddl-rowsecurity.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-rowsecurity.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-rowsecurity.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/ddl-schemas.html postgresql-13-13.14/doc/src/sgml/html/ddl-schemas.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-schemas.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-schemas.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/ddl-system-columns.html postgresql-13-13.14/doc/src/sgml/html/ddl-system-columns.html --- postgresql-13-13.13/doc/src/sgml/html/ddl-system-columns.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl-system-columns.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/ddl.html postgresql-13-13.14/doc/src/sgml/html/ddl.html --- postgresql-13-13.13/doc/src/sgml/html/ddl.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ddl.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/default-roles.html postgresql-13-13.14/doc/src/sgml/html/default-roles.html --- postgresql-13-13.13/doc/src/sgml/html/default-roles.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/default-roles.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/dict-int.html postgresql-13-13.14/doc/src/sgml/html/dict-int.html --- postgresql-13-13.13/doc/src/sgml/html/dict-int.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dict-int.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/dict-xsyn.html postgresql-13-13.14/doc/src/sgml/html/dict-xsyn.html --- postgresql-13-13.13/doc/src/sgml/html/dict-xsyn.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dict-xsyn.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/different-replication-solutions.html postgresql-13-13.14/doc/src/sgml/html/different-replication-solutions.html --- postgresql-13-13.13/doc/src/sgml/html/different-replication-solutions.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/different-replication-solutions.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/disk-full.html postgresql-13-13.14/doc/src/sgml/html/disk-full.html --- postgresql-13-13.13/doc/src/sgml/html/disk-full.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/disk-full.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/disk-usage.html postgresql-13-13.14/doc/src/sgml/html/disk-usage.html --- postgresql-13-13.13/doc/src/sgml/html/disk-usage.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/disk-usage.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/diskusage.html postgresql-13-13.14/doc/src/sgml/html/diskusage.html --- postgresql-13-13.13/doc/src/sgml/html/diskusage.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/diskusage.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/dml-delete.html postgresql-13-13.14/doc/src/sgml/html/dml-delete.html --- postgresql-13-13.13/doc/src/sgml/html/dml-delete.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dml-delete.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/dml-insert.html postgresql-13-13.14/doc/src/sgml/html/dml-insert.html --- postgresql-13-13.13/doc/src/sgml/html/dml-insert.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dml-insert.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/dml-returning.html postgresql-13-13.14/doc/src/sgml/html/dml-returning.html --- postgresql-13-13.13/doc/src/sgml/html/dml-returning.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dml-returning.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/dml-update.html postgresql-13-13.14/doc/src/sgml/html/dml-update.html --- postgresql-13-13.13/doc/src/sgml/html/dml-update.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dml-update.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/dml.html postgresql-13-13.14/doc/src/sgml/html/dml.html --- postgresql-13-13.13/doc/src/sgml/html/dml.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dml.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/docguide-authoring.html postgresql-13-13.14/doc/src/sgml/html/docguide-authoring.html --- postgresql-13-13.13/doc/src/sgml/html/docguide-authoring.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/docguide-authoring.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/docguide-build.html postgresql-13-13.14/doc/src/sgml/html/docguide-build.html --- postgresql-13-13.13/doc/src/sgml/html/docguide-build.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/docguide-build.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/docguide-docbook.html postgresql-13-13.14/doc/src/sgml/html/docguide-docbook.html --- postgresql-13-13.13/doc/src/sgml/html/docguide-docbook.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/docguide-docbook.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/docguide-style.html postgresql-13-13.14/doc/src/sgml/html/docguide-style.html --- postgresql-13-13.13/doc/src/sgml/html/docguide-style.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/docguide-style.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/docguide-toolsets.html postgresql-13-13.14/doc/src/sgml/html/docguide-toolsets.html --- postgresql-13-13.13/doc/src/sgml/html/docguide-toolsets.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/docguide-toolsets.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/docguide.html postgresql-13-13.14/doc/src/sgml/html/docguide.html --- postgresql-13-13.13/doc/src/sgml/html/docguide.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/docguide.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/domains.html postgresql-13-13.14/doc/src/sgml/html/domains.html --- postgresql-13-13.13/doc/src/sgml/html/domains.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/domains.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/dynamic-trace.html postgresql-13-13.14/doc/src/sgml/html/dynamic-trace.html --- postgresql-13-13.13/doc/src/sgml/html/dynamic-trace.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/dynamic-trace.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/earthdistance.html postgresql-13-13.14/doc/src/sgml/html/earthdistance.html --- postgresql-13-13.13/doc/src/sgml/html/earthdistance.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/earthdistance.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/ecpg-commands.html postgresql-13-13.14/doc/src/sgml/html/ecpg-commands.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-commands.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-commands.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-concept.html postgresql-13-13.14/doc/src/sgml/html/ecpg-concept.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-concept.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-concept.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-connect.html postgresql-13-13.14/doc/src/sgml/html/ecpg-connect.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-connect.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-connect.html 2024-02-05 22:04:13.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

    @@ -193,4 +193,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.13/doc/src/sgml/html/ecpg-cpp.html postgresql-13-13.14/doc/src/sgml/html/ecpg-cpp.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-cpp.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-cpp.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-descriptors.html postgresql-13-13.14/doc/src/sgml/html/ecpg-descriptors.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-descriptors.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-descriptors.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-develop.html postgresql-13-13.14/doc/src/sgml/html/ecpg-develop.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-develop.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-develop.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/ecpg-dynamic.html postgresql-13-13.14/doc/src/sgml/html/ecpg-dynamic.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-dynamic.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-dynamic.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-errors.html postgresql-13-13.14/doc/src/sgml/html/ecpg-errors.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-errors.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-errors.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-informix-compat.html postgresql-13-13.14/doc/src/sgml/html/ecpg-informix-compat.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-informix-compat.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-informix-compat.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/ecpg-library.html postgresql-13-13.14/doc/src/sgml/html/ecpg-library.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-library.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-library.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-lo.html postgresql-13-13.14/doc/src/sgml/html/ecpg-lo.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-lo.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-lo.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-oracle-compat.html postgresql-13-13.14/doc/src/sgml/html/ecpg-oracle-compat.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-oracle-compat.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-oracle-compat.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/ecpg-pgtypes.html postgresql-13-13.14/doc/src/sgml/html/ecpg-pgtypes.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-pgtypes.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-pgtypes.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-preproc.html postgresql-13-13.14/doc/src/sgml/html/ecpg-preproc.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-preproc.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-preproc.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-process.html postgresql-13-13.14/doc/src/sgml/html/ecpg-process.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-process.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-process.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-allocate-descriptor.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-commands.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-commands.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-commands.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-commands.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-connect.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-connect.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-connect.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-connect.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-deallocate-descriptor.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-declare.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-declare.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-declare.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-declare.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-describe.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-describe.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-describe.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-describe.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-disconnect.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-disconnect.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-disconnect.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-disconnect.html 2024-02-05 22:04:13.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 ALL
@@ -32,4 +32,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.13/doc/src/sgml/html/ecpg-sql-execute-immediate.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-execute-immediate.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-execute-immediate.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-execute-immediate.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-get-descriptor.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-get-descriptor.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-get-descriptor.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-get-descriptor.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-open.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-open.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-open.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-open.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-prepare.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-prepare.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-prepare.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-prepare.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-set-autocommit.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-set-autocommit.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-set-autocommit.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-set-autocommit.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-set-connection.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-set-connection.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-set-connection.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-set-connection.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-set-descriptor.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-set-descriptor.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-set-descriptor.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-set-descriptor.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-type.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-type.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-type.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-type.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-var.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-var.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-var.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-var.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-sql-whenever.html postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-whenever.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-sql-whenever.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-sql-whenever.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg-variables.html postgresql-13-13.14/doc/src/sgml/html/ecpg-variables.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg-variables.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg-variables.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/ecpg.html postgresql-13-13.14/doc/src/sgml/html/ecpg.html --- postgresql-13-13.13/doc/src/sgml/html/ecpg.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ecpg.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/encryption-options.html postgresql-13-13.14/doc/src/sgml/html/encryption-options.html --- postgresql-13-13.13/doc/src/sgml/html/encryption-options.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/encryption-options.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/errcodes-appendix.html postgresql-13-13.14/doc/src/sgml/html/errcodes-appendix.html --- postgresql-13-13.13/doc/src/sgml/html/errcodes-appendix.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/errcodes-appendix.html 2024-02-05 22:04:29.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.13. (Some are not actually + PostgreSQL 13.14. (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.13/doc/src/sgml/html/error-message-reporting.html postgresql-13-13.14/doc/src/sgml/html/error-message-reporting.html --- postgresql-13-13.13/doc/src/sgml/html/error-message-reporting.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/error-message-reporting.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/error-style-guide.html postgresql-13-13.14/doc/src/sgml/html/error-style-guide.html --- postgresql-13-13.13/doc/src/sgml/html/error-style-guide.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/error-style-guide.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/event-log-registration.html postgresql-13-13.14/doc/src/sgml/html/event-log-registration.html --- postgresql-13-13.13/doc/src/sgml/html/event-log-registration.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-log-registration.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/event-trigger-definition.html postgresql-13-13.14/doc/src/sgml/html/event-trigger-definition.html --- postgresql-13-13.13/doc/src/sgml/html/event-trigger-definition.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-trigger-definition.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/event-trigger-example.html postgresql-13-13.14/doc/src/sgml/html/event-trigger-example.html --- postgresql-13-13.13/doc/src/sgml/html/event-trigger-example.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-trigger-example.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/event-trigger-interface.html postgresql-13-13.14/doc/src/sgml/html/event-trigger-interface.html --- postgresql-13-13.13/doc/src/sgml/html/event-trigger-interface.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-trigger-interface.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/event-trigger-matrix.html postgresql-13-13.14/doc/src/sgml/html/event-trigger-matrix.html --- postgresql-13-13.13/doc/src/sgml/html/event-trigger-matrix.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-trigger-matrix.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/event-trigger-table-rewrite-example.html postgresql-13-13.14/doc/src/sgml/html/event-trigger-table-rewrite-example.html --- postgresql-13-13.13/doc/src/sgml/html/event-trigger-table-rewrite-example.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-trigger-table-rewrite-example.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/event-triggers.html postgresql-13-13.14/doc/src/sgml/html/event-triggers.html --- postgresql-13-13.13/doc/src/sgml/html/event-triggers.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/event-triggers.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/executor.html postgresql-13-13.14/doc/src/sgml/html/executor.html --- postgresql-13-13.13/doc/src/sgml/html/executor.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/executor.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/explicit-joins.html postgresql-13-13.14/doc/src/sgml/html/explicit-joins.html --- postgresql-13-13.13/doc/src/sgml/html/explicit-joins.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/explicit-joins.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/explicit-locking.html postgresql-13-13.14/doc/src/sgml/html/explicit-locking.html --- postgresql-13-13.13/doc/src/sgml/html/explicit-locking.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/explicit-locking.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/extend-extensions.html postgresql-13-13.14/doc/src/sgml/html/extend-extensions.html --- postgresql-13-13.13/doc/src/sgml/html/extend-extensions.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/extend-extensions.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/extend-how.html postgresql-13-13.14/doc/src/sgml/html/extend-how.html --- postgresql-13-13.13/doc/src/sgml/html/extend-how.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/extend-how.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/extend-pgxs.html postgresql-13-13.14/doc/src/sgml/html/extend-pgxs.html --- postgresql-13-13.13/doc/src/sgml/html/extend-pgxs.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/extend-pgxs.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/extend-type-system.html postgresql-13-13.14/doc/src/sgml/html/extend-type-system.html --- postgresql-13-13.13/doc/src/sgml/html/extend-type-system.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/extend-type-system.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/extend.html postgresql-13-13.14/doc/src/sgml/html/extend.html --- postgresql-13-13.13/doc/src/sgml/html/extend.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/extend.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/external-admin-tools.html postgresql-13-13.14/doc/src/sgml/html/external-admin-tools.html --- postgresql-13-13.13/doc/src/sgml/html/external-admin-tools.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/external-admin-tools.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/external-extensions.html postgresql-13-13.14/doc/src/sgml/html/external-extensions.html --- postgresql-13-13.13/doc/src/sgml/html/external-extensions.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/external-extensions.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/external-interfaces.html postgresql-13-13.14/doc/src/sgml/html/external-interfaces.html --- postgresql-13-13.13/doc/src/sgml/html/external-interfaces.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/external-interfaces.html 2024-02-05 22:04:33.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 +

    Prev Up Next
    Appendix H. External Projects Home H.2. Administration Tools
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/external-pl.html postgresql-13-13.14/doc/src/sgml/html/external-pl.html --- postgresql-13-13.13/doc/src/sgml/html/external-pl.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/external-pl.html 2024-02-05 22:04:33.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. @@ -15,4 +15,4 @@ and documentation.

    https://wiki.postgresql.org/wiki/PL_Matrix -

    Prev Up Next
    H.2. Administration Tools Home H.4. Extensions
    \ No newline at end of file +

    Prev Up Next
    H.2. Administration Tools Home H.4. Extensions
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/external-projects.html postgresql-13-13.14/doc/src/sgml/html/external-projects.html --- postgresql-13-13.13/doc/src/sgml/html/external-projects.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/external-projects.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/fdw-callbacks.html postgresql-13-13.14/doc/src/sgml/html/fdw-callbacks.html --- postgresql-13-13.13/doc/src/sgml/html/fdw-callbacks.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fdw-callbacks.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/fdw-functions.html postgresql-13-13.14/doc/src/sgml/html/fdw-functions.html --- postgresql-13-13.13/doc/src/sgml/html/fdw-functions.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fdw-functions.html 2024-02-05 22:04:28.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. @@ -24,13 +24,10 @@ foreign tables using the wrapper. The validator function must be registered as taking two arguments, a text array containing the options to be validated, and an OID - representing the type of object the options are associated with (in - the form of the OID of the system catalog the object would be stored - in, either - ForeignDataWrapperRelationId, - ForeignServerRelationId, - UserMappingRelationId, - or ForeignTableRelationId). + representing the type of object the options are associated with. The + latter corresponds to the OID of the system catalog the object + would be stored in, one of: +

    • AttributeRelationId

    • ForeignDataWrapperRelationId

    • ForeignServerRelationId

    • ForeignTableRelationId

    • UserMappingRelationId

    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.13/doc/src/sgml/html/fdw-helpers.html postgresql-13-13.14/doc/src/sgml/html/fdw-helpers.html --- postgresql-13-13.13/doc/src/sgml/html/fdw-helpers.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fdw-helpers.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/fdw-planning.html postgresql-13-13.14/doc/src/sgml/html/fdw-planning.html --- postgresql-13-13.13/doc/src/sgml/html/fdw-planning.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fdw-planning.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/fdw-row-locking.html postgresql-13-13.14/doc/src/sgml/html/fdw-row-locking.html --- postgresql-13-13.13/doc/src/sgml/html/fdw-row-locking.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fdw-row-locking.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/fdwhandler.html postgresql-13-13.14/doc/src/sgml/html/fdwhandler.html --- postgresql-13-13.13/doc/src/sgml/html/fdwhandler.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fdwhandler.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/features-sql-standard.html postgresql-13-13.14/doc/src/sgml/html/features-sql-standard.html --- postgresql-13-13.13/doc/src/sgml/html/features-sql-standard.html 2023-11-06 22:30:52.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/features-sql-standard.html 2024-02-05 22:04:31.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.13/doc/src/sgml/html/features.html postgresql-13-13.14/doc/src/sgml/html/features.html --- postgresql-13-13.13/doc/src/sgml/html/features.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/features.html 2024-02-05 22:04:31.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.13/doc/src/sgml/html/file-fdw.html postgresql-13-13.14/doc/src/sgml/html/file-fdw.html --- postgresql-13-13.13/doc/src/sgml/html/file-fdw.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/file-fdw.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/functions-admin.html postgresql-13-13.14/doc/src/sgml/html/functions-admin.html --- postgresql-13-13.13/doc/src/sgml/html/functions-admin.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-admin.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/functions-aggregate.html postgresql-13-13.14/doc/src/sgml/html/functions-aggregate.html --- postgresql-13-13.13/doc/src/sgml/html/functions-aggregate.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-aggregate.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-array.html postgresql-13-13.14/doc/src/sgml/html/functions-array.html --- postgresql-13-13.13/doc/src/sgml/html/functions-array.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-array.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-binarystring.html postgresql-13-13.14/doc/src/sgml/html/functions-binarystring.html --- postgresql-13-13.13/doc/src/sgml/html/functions-binarystring.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-binarystring.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-bitstring.html postgresql-13-13.14/doc/src/sgml/html/functions-bitstring.html --- postgresql-13-13.13/doc/src/sgml/html/functions-bitstring.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-bitstring.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-comparison.html postgresql-13-13.14/doc/src/sgml/html/functions-comparison.html --- postgresql-13-13.13/doc/src/sgml/html/functions-comparison.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-comparison.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-comparisons.html postgresql-13-13.14/doc/src/sgml/html/functions-comparisons.html --- postgresql-13-13.13/doc/src/sgml/html/functions-comparisons.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-comparisons.html 2024-02-05 22:04:07.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, @@ -212,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.13/doc/src/sgml/html/functions-conditional.html postgresql-13-13.14/doc/src/sgml/html/functions-conditional.html --- postgresql-13-13.13/doc/src/sgml/html/functions-conditional.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-conditional.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-datetime.html postgresql-13-13.14/doc/src/sgml/html/functions-datetime.html --- postgresql-13-13.13/doc/src/sgml/html/functions-datetime.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-datetime.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-enum.html postgresql-13-13.14/doc/src/sgml/html/functions-enum.html --- postgresql-13-13.13/doc/src/sgml/html/functions-enum.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-enum.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-event-triggers.html postgresql-13-13.14/doc/src/sgml/html/functions-event-triggers.html --- postgresql-13-13.13/doc/src/sgml/html/functions-event-triggers.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-event-triggers.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/functions-formatting.html postgresql-13-13.14/doc/src/sgml/html/functions-formatting.html --- postgresql-13-13.13/doc/src/sgml/html/functions-formatting.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-formatting.html 2024-02-05 22:04:06.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 @@ -407,4 +407,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.13/doc/src/sgml/html/functions-geometry.html postgresql-13-13.14/doc/src/sgml/html/functions-geometry.html --- postgresql-13-13.13/doc/src/sgml/html/functions-geometry.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-geometry.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-info.html postgresql-13-13.14/doc/src/sgml/html/functions-info.html --- postgresql-13-13.13/doc/src/sgml/html/functions-info.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-info.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/functions-json.html postgresql-13-13.14/doc/src/sgml/html/functions-json.html --- postgresql-13-13.13/doc/src/sgml/html/functions-json.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-json.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-logical.html postgresql-13-13.14/doc/src/sgml/html/functions-logical.html --- postgresql-13-13.13/doc/src/sgml/html/functions-logical.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-logical.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-matching.html postgresql-13-13.14/doc/src/sgml/html/functions-matching.html --- postgresql-13-13.13/doc/src/sgml/html/functions-matching.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-matching.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-math.html postgresql-13-13.14/doc/src/sgml/html/functions-math.html --- postgresql-13-13.13/doc/src/sgml/html/functions-math.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-math.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-net.html postgresql-13-13.14/doc/src/sgml/html/functions-net.html --- postgresql-13-13.13/doc/src/sgml/html/functions-net.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-net.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-range.html postgresql-13-13.14/doc/src/sgml/html/functions-range.html --- postgresql-13-13.13/doc/src/sgml/html/functions-range.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-range.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-sequence.html postgresql-13-13.14/doc/src/sgml/html/functions-sequence.html --- postgresql-13-13.13/doc/src/sgml/html/functions-sequence.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-sequence.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-srf.html postgresql-13-13.14/doc/src/sgml/html/functions-srf.html --- postgresql-13-13.13/doc/src/sgml/html/functions-srf.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-srf.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-statistics.html postgresql-13-13.14/doc/src/sgml/html/functions-statistics.html --- postgresql-13-13.13/doc/src/sgml/html/functions-statistics.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-statistics.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/functions-string.html postgresql-13-13.14/doc/src/sgml/html/functions-string.html --- postgresql-13-13.13/doc/src/sgml/html/functions-string.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-string.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/functions-subquery.html postgresql-13-13.14/doc/src/sgml/html/functions-subquery.html --- postgresql-13-13.13/doc/src/sgml/html/functions-subquery.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-subquery.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-textsearch.html postgresql-13-13.14/doc/src/sgml/html/functions-textsearch.html --- postgresql-13-13.13/doc/src/sgml/html/functions-textsearch.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-textsearch.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-trigger.html postgresql-13-13.14/doc/src/sgml/html/functions-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/functions-trigger.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-trigger.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/functions-uuid.html postgresql-13-13.14/doc/src/sgml/html/functions-uuid.html --- postgresql-13-13.13/doc/src/sgml/html/functions-uuid.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-uuid.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-window.html postgresql-13-13.14/doc/src/sgml/html/functions-window.html --- postgresql-13-13.13/doc/src/sgml/html/functions-window.html 2023-11-06 22:30:28.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-window.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions-xml.html postgresql-13-13.14/doc/src/sgml/html/functions-xml.html --- postgresql-13-13.13/doc/src/sgml/html/functions-xml.html 2023-11-06 22:30:27.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions-xml.html 2024-02-05 22:04:07.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.13/doc/src/sgml/html/functions.html postgresql-13-13.14/doc/src/sgml/html/functions.html --- postgresql-13-13.13/doc/src/sgml/html/functions.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/functions.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/fuzzystrmatch.html postgresql-13-13.14/doc/src/sgml/html/fuzzystrmatch.html --- postgresql-13-13.13/doc/src/sgml/html/fuzzystrmatch.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/fuzzystrmatch.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/generic-wal.html postgresql-13-13.14/doc/src/sgml/html/generic-wal.html --- postgresql-13-13.13/doc/src/sgml/html/generic-wal.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/generic-wal.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/geqo-biblio.html postgresql-13-13.14/doc/src/sgml/html/geqo-biblio.html --- postgresql-13-13.13/doc/src/sgml/html/geqo-biblio.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/geqo-biblio.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/geqo-intro.html postgresql-13-13.14/doc/src/sgml/html/geqo-intro.html --- postgresql-13-13.13/doc/src/sgml/html/geqo-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/geqo-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/geqo-intro2.html postgresql-13-13.14/doc/src/sgml/html/geqo-intro2.html --- postgresql-13-13.13/doc/src/sgml/html/geqo-intro2.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/geqo-intro2.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/geqo-pg-intro.html postgresql-13-13.14/doc/src/sgml/html/geqo-pg-intro.html --- postgresql-13-13.13/doc/src/sgml/html/geqo-pg-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/geqo-pg-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/geqo.html postgresql-13-13.14/doc/src/sgml/html/geqo.html --- postgresql-13-13.13/doc/src/sgml/html/geqo.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/geqo.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-builtin-opclasses.html postgresql-13-13.14/doc/src/sgml/html/gin-builtin-opclasses.html --- postgresql-13-13.13/doc/src/sgml/html/gin-builtin-opclasses.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-builtin-opclasses.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-examples.html postgresql-13-13.14/doc/src/sgml/html/gin-examples.html --- postgresql-13-13.13/doc/src/sgml/html/gin-examples.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-examples.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-extensibility.html postgresql-13-13.14/doc/src/sgml/html/gin-extensibility.html --- postgresql-13-13.13/doc/src/sgml/html/gin-extensibility.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-extensibility.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-implementation.html postgresql-13-13.14/doc/src/sgml/html/gin-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/gin-implementation.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-implementation.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-intro.html postgresql-13-13.14/doc/src/sgml/html/gin-intro.html --- postgresql-13-13.13/doc/src/sgml/html/gin-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-limit.html postgresql-13-13.14/doc/src/sgml/html/gin-limit.html --- postgresql-13-13.13/doc/src/sgml/html/gin-limit.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-limit.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin-tips.html postgresql-13-13.14/doc/src/sgml/html/gin-tips.html --- postgresql-13-13.13/doc/src/sgml/html/gin-tips.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin-tips.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gin.html postgresql-13-13.14/doc/src/sgml/html/gin.html --- postgresql-13-13.13/doc/src/sgml/html/gin.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gin.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gist-builtin-opclasses.html postgresql-13-13.14/doc/src/sgml/html/gist-builtin-opclasses.html --- postgresql-13-13.13/doc/src/sgml/html/gist-builtin-opclasses.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gist-builtin-opclasses.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gist-examples.html postgresql-13-13.14/doc/src/sgml/html/gist-examples.html --- postgresql-13-13.13/doc/src/sgml/html/gist-examples.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gist-examples.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gist-extensibility.html postgresql-13-13.14/doc/src/sgml/html/gist-extensibility.html --- postgresql-13-13.13/doc/src/sgml/html/gist-extensibility.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gist-extensibility.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gist-implementation.html postgresql-13-13.14/doc/src/sgml/html/gist-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/gist-implementation.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gist-implementation.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gist-intro.html postgresql-13-13.14/doc/src/sgml/html/gist-intro.html --- postgresql-13-13.13/doc/src/sgml/html/gist-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gist-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/gist.html postgresql-13-13.14/doc/src/sgml/html/gist.html --- postgresql-13-13.13/doc/src/sgml/html/gist.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gist.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/git.html postgresql-13-13.14/doc/src/sgml/html/git.html --- postgresql-13-13.13/doc/src/sgml/html/git.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/git.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/glossary.html postgresql-13-13.14/doc/src/sgml/html/glossary.html --- postgresql-13-13.13/doc/src/sgml/html/glossary.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/glossary.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/gssapi-auth.html postgresql-13-13.14/doc/src/sgml/html/gssapi-auth.html --- postgresql-13-13.13/doc/src/sgml/html/gssapi-auth.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gssapi-auth.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/gssapi-enc.html postgresql-13-13.14/doc/src/sgml/html/gssapi-enc.html --- postgresql-13-13.13/doc/src/sgml/html/gssapi-enc.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/gssapi-enc.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/hash-implementation.html postgresql-13-13.14/doc/src/sgml/html/hash-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/hash-implementation.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/hash-implementation.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/hash-index.html postgresql-13-13.14/doc/src/sgml/html/hash-index.html --- postgresql-13-13.13/doc/src/sgml/html/hash-index.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/hash-index.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/hash-intro.html postgresql-13-13.14/doc/src/sgml/html/hash-intro.html --- postgresql-13-13.13/doc/src/sgml/html/hash-intro.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/hash-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/high-availability.html postgresql-13-13.14/doc/src/sgml/html/high-availability.html --- postgresql-13-13.13/doc/src/sgml/html/high-availability.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/high-availability.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/history.html postgresql-13-13.14/doc/src/sgml/html/history.html --- postgresql-13-13.13/doc/src/sgml/html/history.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/history.html 2024-02-05 22:04:04.000000000 +0000 @@ -1,5 +1,5 @@ -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 @@ -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.13/doc/src/sgml/html/hot-standby.html postgresql-13-13.14/doc/src/sgml/html/hot-standby.html --- postgresql-13-13.13/doc/src/sgml/html/hot-standby.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/hot-standby.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/how-parallel-query-works.html postgresql-13-13.14/doc/src/sgml/html/how-parallel-query-works.html --- postgresql-13-13.13/doc/src/sgml/html/how-parallel-query-works.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/how-parallel-query-works.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/hstore.html postgresql-13-13.14/doc/src/sgml/html/hstore.html --- postgresql-13-13.13/doc/src/sgml/html/hstore.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/hstore.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/index-api.html postgresql-13-13.14/doc/src/sgml/html/index-api.html --- postgresql-13-13.13/doc/src/sgml/html/index-api.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index-api.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/index-cost-estimation.html postgresql-13-13.14/doc/src/sgml/html/index-cost-estimation.html --- postgresql-13-13.13/doc/src/sgml/html/index-cost-estimation.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index-cost-estimation.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/index-functions.html postgresql-13-13.14/doc/src/sgml/html/index-functions.html --- postgresql-13-13.13/doc/src/sgml/html/index-functions.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index-functions.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/index-locking.html postgresql-13-13.14/doc/src/sgml/html/index-locking.html --- postgresql-13-13.13/doc/src/sgml/html/index-locking.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index-locking.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/index-scanning.html postgresql-13-13.14/doc/src/sgml/html/index-scanning.html --- postgresql-13-13.13/doc/src/sgml/html/index-scanning.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index-scanning.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/index-unique-checks.html postgresql-13-13.14/doc/src/sgml/html/index-unique-checks.html --- postgresql-13-13.13/doc/src/sgml/html/index-unique-checks.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index-unique-checks.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/index.html postgresql-13-13.14/doc/src/sgml/html/index.html --- postgresql-13-13.13/doc/src/sgml/html/index.html 2023-11-06 22:30:57.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/index.html 2024-02-05 22:04:36.000000000 +0000 @@ -1,2 +1,2 @@ -PostgreSQL 13.13 Documentation
    PostgreSQL 13.13 Documentation
         Next

    PostgreSQL 13.13 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.14 Documentation
    PostgreSQL 13.14 Documentation
         Next

    PostgreSQL 13.14 Documentation

    The PostgreSQL Global Development Group

    Copyright © 1996–2024 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.13/doc/src/sgml/html/indexam.html postgresql-13-13.14/doc/src/sgml/html/indexam.html --- postgresql-13-13.13/doc/src/sgml/html/indexam.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexam.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/indexes-bitmap-scans.html postgresql-13-13.14/doc/src/sgml/html/indexes-bitmap-scans.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-bitmap-scans.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-bitmap-scans.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-collations.html postgresql-13-13.14/doc/src/sgml/html/indexes-collations.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-collations.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-collations.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-examine.html postgresql-13-13.14/doc/src/sgml/html/indexes-examine.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-examine.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-examine.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-expressional.html postgresql-13-13.14/doc/src/sgml/html/indexes-expressional.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-expressional.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-expressional.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-index-only-scans.html postgresql-13-13.14/doc/src/sgml/html/indexes-index-only-scans.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-index-only-scans.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-index-only-scans.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-intro.html postgresql-13-13.14/doc/src/sgml/html/indexes-intro.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-intro.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-intro.html 2024-02-05 22:04:08.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 (
@@ -59,6 +59,35 @@
    an index defined on a column that is part of a join condition can
    also significantly speed up queries with joins.
   
    
+   In general, PostgreSQL indexes can be used
+   to optimize queries that contain one or more WHERE
+   or JOIN clauses of the form
+
+
    +indexed-column indexable-operator comparison-value
+
    
+
+   Here, the indexed-column is whatever
+   column or expression the index has been defined on.
+   The indexable-operator is an operator that
+   is a member of the index's operator class for
+   the indexed column.  (More details about that appear below.)
+   And the comparison-value can be any
+   expression that is not volatile and does not reference the index's
+   table.
+  
    
+   In some cases the query planner can extract an indexable clause of
+   this form from another SQL construct.  A simple example is that if
+   the original clause was
+
+
    +comparison-value operator indexed-column
+
    
+
+   then it can be flipped around into indexable form if the
+   original operator has a commutator
+   operator that is a member of the index's operator class.
+  
    
    Creating an index on a large table can take a long time.  By default,
    PostgreSQL allows reads (SELECT statements) to occur
    on the table in parallel with index creation, but writes (INSERT,
@@ -74,4 +103,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.13/doc/src/sgml/html/indexes-multicolumn.html postgresql-13-13.14/doc/src/sgml/html/indexes-multicolumn.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-multicolumn.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-multicolumn.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-opclass.html postgresql-13-13.14/doc/src/sgml/html/indexes-opclass.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-opclass.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-opclass.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-ordering.html postgresql-13-13.14/doc/src/sgml/html/indexes-ordering.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-ordering.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-ordering.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-partial.html postgresql-13-13.14/doc/src/sgml/html/indexes-partial.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-partial.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-partial.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes-types.html postgresql-13-13.14/doc/src/sgml/html/indexes-types.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-types.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-types.html 2024-02-05 22:04:08.000000000 +0000 @@ -1,9 +1,9 @@ -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 - algorithm that is best suited to different types of queries. + algorithm that is best suited to different types of indexable clauses. By default, the CREATE INDEX command creates B-tree indexes, which fit the most common situations.

    @@ -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.13/doc/src/sgml/html/indexes-unique.html postgresql-13-13.14/doc/src/sgml/html/indexes-unique.html --- postgresql-13-13.13/doc/src/sgml/html/indexes-unique.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes-unique.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/indexes.html postgresql-13-13.14/doc/src/sgml/html/indexes.html --- postgresql-13-13.13/doc/src/sgml/html/indexes.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/indexes.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/information-schema.html postgresql-13-13.14/doc/src/sgml/html/information-schema.html --- postgresql-13-13.13/doc/src/sgml/html/information-schema.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/information-schema.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-administrable-role-authorizations.html postgresql-13-13.14/doc/src/sgml/html/infoschema-administrable-role-authorizations.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-administrable-role-authorizations.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-applicable-roles.html postgresql-13-13.14/doc/src/sgml/html/infoschema-applicable-roles.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-applicable-roles.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-applicable-roles.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-attributes.html postgresql-13-13.14/doc/src/sgml/html/infoschema-attributes.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-attributes.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-attributes.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-character-sets.html postgresql-13-13.14/doc/src/sgml/html/infoschema-character-sets.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-character-sets.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-character-sets.html 2024-02-05 22:04:14.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 @@ -14,8 +14,8 @@

    character encoding form

    An encoding of some character repertoire. Most older character repertoires only use one encoding form, and so there are no - separate names for them (e.g., LATIN1 is an - encoding form applicable to the LATIN1 + separate names for them (e.g., LATIN2 is an + encoding form applicable to the LATIN2 repertoire). But for example Unicode has the encoding forms UTF8, UTF16, etc. (not all supported by PostgreSQL). Encoding forms are not exposed @@ -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.13/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-check-constraint-routine-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-check-constraints.html postgresql-13-13.14/doc/src/sgml/html/infoschema-check-constraints.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-check-constraints.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-check-constraints.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-collation-character-set-applicab.html postgresql-13-13.14/doc/src/sgml/html/infoschema-collation-character-set-applicab.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-collation-character-set-applicab.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-collations.html postgresql-13-13.14/doc/src/sgml/html/infoschema-collations.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-collations.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-collations.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-column-column-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-column-column-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-column-column-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-column-column-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-column-domain-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-column-domain-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-column-domain-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-column-domain-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-column-options.html postgresql-13-13.14/doc/src/sgml/html/infoschema-column-options.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-column-options.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-column-options.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-column-privileges.html postgresql-13-13.14/doc/src/sgml/html/infoschema-column-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-column-privileges.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-column-privileges.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-column-udt-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-column-udt-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-column-udt-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-column-udt-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-columns.html postgresql-13-13.14/doc/src/sgml/html/infoschema-columns.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-columns.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-columns.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-constraint-column-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-constraint-column-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-constraint-column-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-constraint-column-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-constraint-table-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-constraint-table-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-constraint-table-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-constraint-table-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-data-type-privileges.html postgresql-13-13.14/doc/src/sgml/html/infoschema-data-type-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-data-type-privileges.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-data-type-privileges.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-datatypes.html postgresql-13-13.14/doc/src/sgml/html/infoschema-datatypes.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-datatypes.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-datatypes.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-domain-constraints.html postgresql-13-13.14/doc/src/sgml/html/infoschema-domain-constraints.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-domain-constraints.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-domain-constraints.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-domain-udt-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-domain-udt-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-domain-udt-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-domain-udt-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-domains.html postgresql-13-13.14/doc/src/sgml/html/infoschema-domains.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-domains.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-domains.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-element-types.html postgresql-13-13.14/doc/src/sgml/html/infoschema-element-types.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-element-types.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-element-types.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-enabled-roles.html postgresql-13-13.14/doc/src/sgml/html/infoschema-enabled-roles.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-enabled-roles.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-enabled-roles.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-data-wrapper-options.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-foreign-data-wrappers.html postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-data-wrappers.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-data-wrappers.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-foreign-server-options.html postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-server-options.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-foreign-server-options.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-server-options.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-foreign-servers.html postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-servers.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-foreign-servers.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-servers.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-foreign-table-options.html postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-table-options.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-foreign-table-options.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-table-options.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-foreign-tables.html postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-tables.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-foreign-tables.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-foreign-tables.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-information-schema-catalog-name.html postgresql-13-13.14/doc/src/sgml/html/infoschema-information-schema-catalog-name.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-information-schema-catalog-name.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-key-column-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-key-column-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-key-column-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-key-column-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-parameters.html postgresql-13-13.14/doc/src/sgml/html/infoschema-parameters.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-parameters.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-parameters.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-referential-constraints.html postgresql-13-13.14/doc/src/sgml/html/infoschema-referential-constraints.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-referential-constraints.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-referential-constraints.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-role-column-grants.html postgresql-13-13.14/doc/src/sgml/html/infoschema-role-column-grants.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-role-column-grants.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-role-column-grants.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-role-routine-grants.html postgresql-13-13.14/doc/src/sgml/html/infoschema-role-routine-grants.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-role-routine-grants.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-role-routine-grants.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-role-table-grants.html postgresql-13-13.14/doc/src/sgml/html/infoschema-role-table-grants.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-role-table-grants.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-role-table-grants.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-role-udt-grants.html postgresql-13-13.14/doc/src/sgml/html/infoschema-role-udt-grants.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-role-udt-grants.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-role-udt-grants.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-role-usage-grants.html postgresql-13-13.14/doc/src/sgml/html/infoschema-role-usage-grants.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-role-usage-grants.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-role-usage-grants.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-routine-privileges.html postgresql-13-13.14/doc/src/sgml/html/infoschema-routine-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-routine-privileges.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-routine-privileges.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-routines.html postgresql-13-13.14/doc/src/sgml/html/infoschema-routines.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-routines.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-routines.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-schema.html postgresql-13-13.14/doc/src/sgml/html/infoschema-schema.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-schema.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-schema.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-schemata.html postgresql-13-13.14/doc/src/sgml/html/infoschema-schemata.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-schemata.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-schemata.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-sequences.html postgresql-13-13.14/doc/src/sgml/html/infoschema-sequences.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-sequences.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-sequences.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-sql-features.html postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-features.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-sql-features.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-features.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-sql-implementation-info.html postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-implementation-info.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-sql-implementation-info.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-implementation-info.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-sql-parts.html postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-parts.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-sql-parts.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-parts.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-sql-sizing.html postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-sizing.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-sql-sizing.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-sql-sizing.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-table-constraints.html postgresql-13-13.14/doc/src/sgml/html/infoschema-table-constraints.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-table-constraints.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-table-constraints.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-table-privileges.html postgresql-13-13.14/doc/src/sgml/html/infoschema-table-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-table-privileges.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-table-privileges.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-tables.html postgresql-13-13.14/doc/src/sgml/html/infoschema-tables.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-tables.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-tables.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-transforms.html postgresql-13-13.14/doc/src/sgml/html/infoschema-transforms.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-transforms.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-transforms.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-triggered-update-columns.html postgresql-13-13.14/doc/src/sgml/html/infoschema-triggered-update-columns.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-triggered-update-columns.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-triggered-update-columns.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-triggers.html postgresql-13-13.14/doc/src/sgml/html/infoschema-triggers.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-triggers.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-triggers.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-udt-privileges.html postgresql-13-13.14/doc/src/sgml/html/infoschema-udt-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-udt-privileges.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-udt-privileges.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-usage-privileges.html postgresql-13-13.14/doc/src/sgml/html/infoschema-usage-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-usage-privileges.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-usage-privileges.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-user-defined-types.html postgresql-13-13.14/doc/src/sgml/html/infoschema-user-defined-types.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-user-defined-types.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-user-defined-types.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-user-mapping-options.html postgresql-13-13.14/doc/src/sgml/html/infoschema-user-mapping-options.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-user-mapping-options.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-user-mapping-options.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-user-mappings.html postgresql-13-13.14/doc/src/sgml/html/infoschema-user-mappings.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-user-mappings.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-user-mappings.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-view-column-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-view-column-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-view-column-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-view-column-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-view-routine-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-view-routine-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-view-routine-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-view-routine-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-view-table-usage.html postgresql-13-13.14/doc/src/sgml/html/infoschema-view-table-usage.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-view-table-usage.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-view-table-usage.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/infoschema-views.html postgresql-13-13.14/doc/src/sgml/html/infoschema-views.html --- postgresql-13-13.13/doc/src/sgml/html/infoschema-views.html 2023-11-06 22:30:35.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/infoschema-views.html 2024-02-05 22:04:14.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.13/doc/src/sgml/html/install-getsource.html postgresql-13-13.14/doc/src/sgml/html/install-getsource.html --- postgresql-13-13.13/doc/src/sgml/html/install-getsource.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-getsource.html 2024-02-05 22:04:09.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.13 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.14 sources can be obtained from the download section of our website: https://www.postgresql.org/download/. You - should get a file named postgresql-13.13.tar.gz - or postgresql-13.13.tar.bz2. After + should get a file named postgresql-13.14.tar.gz + or postgresql-13.14.tar.bz2. After you have obtained the file, unpack it: 

    -gunzip postgresql-13.13.tar.gz
-tar xf postgresql-13.13.tar
+gunzip postgresql-13.14.tar.gz
+tar xf postgresql-13.14.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.13 under the current directory + postgresql-13.14 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.13/doc/src/sgml/html/install-post.html postgresql-13-13.14/doc/src/sgml/html/install-post.html --- postgresql-13-13.13/doc/src/sgml/html/install-post.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-post.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/install-procedure.html postgresql-13-13.14/doc/src/sgml/html/install-procedure.html --- postgresql-13-13.13/doc/src/sgml/html/install-procedure.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-procedure.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/install-requirements.html postgresql-13-13.14/doc/src/sgml/html/install-requirements.html --- postgresql-13-13.13/doc/src/sgml/html/install-requirements.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-requirements.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/install-short.html postgresql-13-13.14/doc/src/sgml/html/install-short.html --- postgresql-13-13.13/doc/src/sgml/html/install-short.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-short.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/install-windows-full.html postgresql-13-13.14/doc/src/sgml/html/install-windows-full.html --- postgresql-13-13.13/doc/src/sgml/html/install-windows-full.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-windows-full.html 2024-02-05 22:04:09.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, @@ -312,4 +312,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.13/doc/src/sgml/html/install-windows.html postgresql-13-13.14/doc/src/sgml/html/install-windows.html --- postgresql-13-13.13/doc/src/sgml/html/install-windows.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/install-windows.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/installation-platform-notes.html postgresql-13-13.14/doc/src/sgml/html/installation-platform-notes.html --- postgresql-13-13.13/doc/src/sgml/html/installation-platform-notes.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/installation-platform-notes.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/installation.html postgresql-13-13.14/doc/src/sgml/html/installation.html --- postgresql-13-13.13/doc/src/sgml/html/installation.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/installation.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/intagg.html postgresql-13-13.14/doc/src/sgml/html/intagg.html --- postgresql-13-13.13/doc/src/sgml/html/intagg.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/intagg.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/intarray.html postgresql-13-13.14/doc/src/sgml/html/intarray.html --- postgresql-13-13.13/doc/src/sgml/html/intarray.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/intarray.html 2024-02-05 22:04:32.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.13/doc/src/sgml/html/internals.html postgresql-13-13.14/doc/src/sgml/html/internals.html --- postgresql-13-13.13/doc/src/sgml/html/internals.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/internals.html 2024-02-05 22:04:29.000000000 +0000 @@ -1,5 +1,5 @@ -Part VII. Internals
    Part VII. Internals
    Prev UpPostgreSQL 13.13 DocumentationHome Next

    Part VII. Internals

    +Part VII. Internals

    Part VII. Internals
    Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/intro-whatis.html postgresql-13-13.14/doc/src/sgml/html/intro-whatis.html --- postgresql-13-13.13/doc/src/sgml/html/intro-whatis.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/intro-whatis.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/isn.html postgresql-13-13.14/doc/src/sgml/html/isn.html --- postgresql-13-13.13/doc/src/sgml/html/isn.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/isn.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/jit-configuration.html postgresql-13-13.14/doc/src/sgml/html/jit-configuration.html --- postgresql-13-13.13/doc/src/sgml/html/jit-configuration.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/jit-configuration.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/jit-decision.html postgresql-13-13.14/doc/src/sgml/html/jit-decision.html --- postgresql-13-13.13/doc/src/sgml/html/jit-decision.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/jit-decision.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/jit-extensibility.html postgresql-13-13.14/doc/src/sgml/html/jit-extensibility.html --- postgresql-13-13.13/doc/src/sgml/html/jit-extensibility.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/jit-extensibility.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/jit-reason.html postgresql-13-13.14/doc/src/sgml/html/jit-reason.html --- postgresql-13-13.13/doc/src/sgml/html/jit-reason.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/jit-reason.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/jit.html postgresql-13-13.14/doc/src/sgml/html/jit.html --- postgresql-13-13.13/doc/src/sgml/html/jit.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/jit.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/kernel-resources.html postgresql-13-13.14/doc/src/sgml/html/kernel-resources.html --- postgresql-13-13.13/doc/src/sgml/html/kernel-resources.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/kernel-resources.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/largeobjects.html postgresql-13-13.14/doc/src/sgml/html/largeobjects.html --- postgresql-13-13.13/doc/src/sgml/html/largeobjects.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/largeobjects.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/legalnotice.html postgresql-13-13.14/doc/src/sgml/html/legalnotice.html --- postgresql-13-13.13/doc/src/sgml/html/legalnotice.html 2023-11-06 22:30:22.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/legalnotice.html 2024-02-05 22:04:01.000000000 +0000 @@ -1,6 +1,6 @@ Legal Notice

    Legal Notice

    - PostgreSQL is Copyright © 1996–2023 + PostgreSQL is Copyright © 1996–2024 by the PostgreSQL Global Development Group.

    Postgres95 is Copyright © 1994–5 diff -Nru postgresql-13-13.13/doc/src/sgml/html/libpq-async.html postgresql-13-13.14/doc/src/sgml/html/libpq-async.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-async.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-async.html 2024-02-05 22:04:13.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: @@ -287,11 +287,12 @@ arg is 1, or blocking if arg is 0. Returns 0 if OK, -1 if error.

    - In the nonblocking state, calls to + In the nonblocking state, successful calls to PQsendQuery, PQputline, PQputnbytes, PQputCopyData, - and PQendcopy will not block but instead return - an error if they need to be called again. + and PQendcopy will not block; their changes + are stored in the local output buffer until they are flushed. + Unsuccessful calls will return an error and must be retried.

    Note that PQexec does not honor nonblocking mode; if it is called, it will act in blocking fashion anyway. @@ -328,4 +329,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.13/doc/src/sgml/html/libpq-build.html postgresql-13-13.14/doc/src/sgml/html/libpq-build.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-build.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-build.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-cancel.html postgresql-13-13.14/doc/src/sgml/html/libpq-cancel.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-cancel.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-cancel.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-connect.html postgresql-13-13.14/doc/src/sgml/html/libpq-connect.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-connect.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-connect.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/libpq-control.html postgresql-13-13.14/doc/src/sgml/html/libpq-control.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-control.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-control.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-copy.html postgresql-13-13.14/doc/src/sgml/html/libpq-copy.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-copy.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-copy.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-envars.html postgresql-13-13.14/doc/src/sgml/html/libpq-envars.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-envars.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-envars.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-events.html postgresql-13-13.14/doc/src/sgml/html/libpq-events.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-events.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-events.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-example.html postgresql-13-13.14/doc/src/sgml/html/libpq-example.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-example.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-example.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-exec.html postgresql-13-13.14/doc/src/sgml/html/libpq-exec.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-exec.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-exec.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/libpq-fastpath.html postgresql-13-13.14/doc/src/sgml/html/libpq-fastpath.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-fastpath.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-fastpath.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-ldap.html postgresql-13-13.14/doc/src/sgml/html/libpq-ldap.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-ldap.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-ldap.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-misc.html postgresql-13-13.14/doc/src/sgml/html/libpq-misc.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-misc.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-misc.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-notice-processing.html postgresql-13-13.14/doc/src/sgml/html/libpq-notice-processing.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-notice-processing.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-notice-processing.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-notify.html postgresql-13-13.14/doc/src/sgml/html/libpq-notify.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-notify.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-notify.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-pgpass.html postgresql-13-13.14/doc/src/sgml/html/libpq-pgpass.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-pgpass.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-pgpass.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-pgservice.html postgresql-13-13.14/doc/src/sgml/html/libpq-pgservice.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-pgservice.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-pgservice.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-single-row-mode.html postgresql-13-13.14/doc/src/sgml/html/libpq-single-row-mode.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-single-row-mode.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-single-row-mode.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-ssl.html postgresql-13-13.14/doc/src/sgml/html/libpq-ssl.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-ssl.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-ssl.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq-status.html postgresql-13-13.14/doc/src/sgml/html/libpq-status.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-status.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-status.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/libpq-threading.html postgresql-13-13.14/doc/src/sgml/html/libpq-threading.html --- postgresql-13-13.13/doc/src/sgml/html/libpq-threading.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq-threading.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/libpq.html postgresql-13-13.14/doc/src/sgml/html/libpq.html --- postgresql-13-13.13/doc/src/sgml/html/libpq.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/libpq.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/limits.html postgresql-13-13.14/doc/src/sgml/html/limits.html --- postgresql-13-13.13/doc/src/sgml/html/limits.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/limits.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/lo-examplesect.html postgresql-13-13.14/doc/src/sgml/html/lo-examplesect.html --- postgresql-13-13.13/doc/src/sgml/html/lo-examplesect.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/lo-examplesect.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/lo-funcs.html postgresql-13-13.14/doc/src/sgml/html/lo-funcs.html --- postgresql-13-13.13/doc/src/sgml/html/lo-funcs.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/lo-funcs.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/lo-implementation.html postgresql-13-13.14/doc/src/sgml/html/lo-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/lo-implementation.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/lo-implementation.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/lo-interfaces.html postgresql-13-13.14/doc/src/sgml/html/lo-interfaces.html --- postgresql-13-13.13/doc/src/sgml/html/lo-interfaces.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/lo-interfaces.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/lo-intro.html postgresql-13-13.14/doc/src/sgml/html/lo-intro.html --- postgresql-13-13.13/doc/src/sgml/html/lo-intro.html 2023-11-06 22:30:34.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/lo-intro.html 2024-02-05 22:04:13.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.13/doc/src/sgml/html/lo.html postgresql-13-13.14/doc/src/sgml/html/lo.html --- postgresql-13-13.13/doc/src/sgml/html/lo.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/lo.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/locale.html postgresql-13-13.14/doc/src/sgml/html/locale.html --- postgresql-13-13.13/doc/src/sgml/html/locale.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/locale.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/locking-indexes.html postgresql-13-13.14/doc/src/sgml/html/locking-indexes.html --- postgresql-13-13.13/doc/src/sgml/html/locking-indexes.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/locking-indexes.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/log-shipping-alternative.html postgresql-13-13.14/doc/src/sgml/html/log-shipping-alternative.html --- postgresql-13-13.13/doc/src/sgml/html/log-shipping-alternative.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/log-shipping-alternative.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/logfile-maintenance.html postgresql-13-13.14/doc/src/sgml/html/logfile-maintenance.html --- postgresql-13-13.13/doc/src/sgml/html/logfile-maintenance.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logfile-maintenance.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/logical-replication-architecture.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-architecture.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-architecture.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-architecture.html 2024-02-05 22:04:12.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 @@ -12,7 +12,8 @@ implemented by “walsender” and “apply” processes. The walsender process starts logical decoding (described in Chapter 48) of the WAL and loads the standard - logical decoding plugin (pgoutput). The plugin transforms the changes read + logical decoding output plugin (pgoutput). The plugin + transforms the changes read from WAL to the logical replication protocol (see Section 52.5) and filters the data according to the publication specification. The data is then continuously @@ -44,4 +45,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.13/doc/src/sgml/html/logical-replication-config.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-config.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-config.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-config.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-conflicts.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-conflicts.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-conflicts.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-conflicts.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-monitoring.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-monitoring.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-monitoring.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-monitoring.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-publication.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-publication.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-publication.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-publication.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-quick-setup.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-quick-setup.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-quick-setup.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-quick-setup.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-restrictions.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-restrictions.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-restrictions.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-restrictions.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-security.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-security.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-security.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-security.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication-subscription.html postgresql-13-13.14/doc/src/sgml/html/logical-replication-subscription.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication-subscription.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication-subscription.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logical-replication.html postgresql-13-13.14/doc/src/sgml/html/logical-replication.html --- postgresql-13-13.13/doc/src/sgml/html/logical-replication.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logical-replication.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/logicaldecoding-catalogs.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-catalogs.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-catalogs.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-catalogs.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-example.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-example.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-example.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-example.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-explanation.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-explanation.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-explanation.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-explanation.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-output-plugin.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-output-plugin.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-output-plugin.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-output-plugin.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-sql.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-sql.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-sql.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-sql.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-synchronous.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-synchronous.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-synchronous.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-synchronous.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-walsender.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-walsender.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-walsender.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-walsender.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding-writer.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-writer.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding-writer.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding-writer.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/logicaldecoding.html postgresql-13-13.14/doc/src/sgml/html/logicaldecoding.html --- postgresql-13-13.13/doc/src/sgml/html/logicaldecoding.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/logicaldecoding.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/ltree.html postgresql-13-13.14/doc/src/sgml/html/ltree.html --- postgresql-13-13.13/doc/src/sgml/html/ltree.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ltree.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/maintenance.html postgresql-13-13.14/doc/src/sgml/html/maintenance.html --- postgresql-13-13.13/doc/src/sgml/html/maintenance.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/maintenance.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/manage-ag-config.html postgresql-13-13.14/doc/src/sgml/html/manage-ag-config.html --- postgresql-13-13.13/doc/src/sgml/html/manage-ag-config.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/manage-ag-config.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/manage-ag-createdb.html postgresql-13-13.14/doc/src/sgml/html/manage-ag-createdb.html --- postgresql-13-13.13/doc/src/sgml/html/manage-ag-createdb.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/manage-ag-createdb.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/manage-ag-dropdb.html postgresql-13-13.14/doc/src/sgml/html/manage-ag-dropdb.html --- postgresql-13-13.13/doc/src/sgml/html/manage-ag-dropdb.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/manage-ag-dropdb.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/manage-ag-overview.html postgresql-13-13.14/doc/src/sgml/html/manage-ag-overview.html --- postgresql-13-13.13/doc/src/sgml/html/manage-ag-overview.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/manage-ag-overview.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/manage-ag-tablespaces.html postgresql-13-13.14/doc/src/sgml/html/manage-ag-tablespaces.html --- postgresql-13-13.13/doc/src/sgml/html/manage-ag-tablespaces.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/manage-ag-tablespaces.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/manage-ag-templatedbs.html postgresql-13-13.14/doc/src/sgml/html/manage-ag-templatedbs.html --- postgresql-13-13.13/doc/src/sgml/html/manage-ag-templatedbs.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/manage-ag-templatedbs.html 2024-02-05 22:04:10.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 @@ -89,4 +89,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.13/doc/src/sgml/html/managing-databases.html postgresql-13-13.14/doc/src/sgml/html/managing-databases.html --- postgresql-13-13.13/doc/src/sgml/html/managing-databases.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/managing-databases.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/monitoring-locks.html postgresql-13-13.14/doc/src/sgml/html/monitoring-locks.html --- postgresql-13-13.13/doc/src/sgml/html/monitoring-locks.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/monitoring-locks.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/monitoring-ps.html postgresql-13-13.14/doc/src/sgml/html/monitoring-ps.html --- postgresql-13-13.13/doc/src/sgml/html/monitoring-ps.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/monitoring-ps.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/monitoring-stats.html postgresql-13-13.14/doc/src/sgml/html/monitoring-stats.html --- postgresql-13-13.13/doc/src/sgml/html/monitoring-stats.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/monitoring-stats.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/monitoring.html postgresql-13-13.14/doc/src/sgml/html/monitoring.html --- postgresql-13-13.13/doc/src/sgml/html/monitoring.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/monitoring.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/multibyte.html postgresql-13-13.14/doc/src/sgml/html/multibyte.html --- postgresql-13-13.13/doc/src/sgml/html/multibyte.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/multibyte.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/multivariate-statistics-examples.html postgresql-13-13.14/doc/src/sgml/html/multivariate-statistics-examples.html --- postgresql-13-13.13/doc/src/sgml/html/multivariate-statistics-examples.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/multivariate-statistics-examples.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/mvcc-caveats.html postgresql-13-13.14/doc/src/sgml/html/mvcc-caveats.html --- postgresql-13-13.13/doc/src/sgml/html/mvcc-caveats.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/mvcc-caveats.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/mvcc-intro.html postgresql-13-13.14/doc/src/sgml/html/mvcc-intro.html --- postgresql-13-13.13/doc/src/sgml/html/mvcc-intro.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/mvcc-intro.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/mvcc.html postgresql-13-13.14/doc/src/sgml/html/mvcc.html --- postgresql-13-13.13/doc/src/sgml/html/mvcc.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/mvcc.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/nls-programmer.html postgresql-13-13.14/doc/src/sgml/html/nls-programmer.html --- postgresql-13-13.13/doc/src/sgml/html/nls-programmer.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/nls-programmer.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/nls-translator.html postgresql-13-13.14/doc/src/sgml/html/nls-translator.html --- postgresql-13-13.13/doc/src/sgml/html/nls-translator.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/nls-translator.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/nls.html postgresql-13-13.14/doc/src/sgml/html/nls.html --- postgresql-13-13.13/doc/src/sgml/html/nls.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/nls.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/non-durability.html postgresql-13-13.14/doc/src/sgml/html/non-durability.html --- postgresql-13-13.13/doc/src/sgml/html/non-durability.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/non-durability.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/notation.html postgresql-13-13.14/doc/src/sgml/html/notation.html --- postgresql-13-13.13/doc/src/sgml/html/notation.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/notation.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/oid2name.html postgresql-13-13.14/doc/src/sgml/html/oid2name.html --- postgresql-13-13.13/doc/src/sgml/html/oid2name.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/oid2name.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/overview.html postgresql-13-13.14/doc/src/sgml/html/overview.html --- postgresql-13-13.13/doc/src/sgml/html/overview.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/overview.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/pageinspect.html postgresql-13-13.14/doc/src/sgml/html/pageinspect.html --- postgresql-13-13.13/doc/src/sgml/html/pageinspect.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pageinspect.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/parallel-plans.html postgresql-13-13.14/doc/src/sgml/html/parallel-plans.html --- postgresql-13-13.13/doc/src/sgml/html/parallel-plans.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/parallel-plans.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/parallel-query.html postgresql-13-13.14/doc/src/sgml/html/parallel-query.html --- postgresql-13-13.13/doc/src/sgml/html/parallel-query.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/parallel-query.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/parallel-safety.html postgresql-13-13.14/doc/src/sgml/html/parallel-safety.html --- postgresql-13-13.13/doc/src/sgml/html/parallel-safety.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/parallel-safety.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/parser-stage.html postgresql-13-13.14/doc/src/sgml/html/parser-stage.html --- postgresql-13-13.13/doc/src/sgml/html/parser-stage.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/parser-stage.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/passwordcheck.html postgresql-13-13.14/doc/src/sgml/html/passwordcheck.html --- postgresql-13-13.13/doc/src/sgml/html/passwordcheck.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/passwordcheck.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/performance-tips.html postgresql-13-13.14/doc/src/sgml/html/performance-tips.html --- postgresql-13-13.13/doc/src/sgml/html/performance-tips.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/performance-tips.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/perm-functions.html postgresql-13-13.14/doc/src/sgml/html/perm-functions.html --- postgresql-13-13.13/doc/src/sgml/html/perm-functions.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/perm-functions.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/pgarchivecleanup.html postgresql-13-13.14/doc/src/sgml/html/pgarchivecleanup.html --- postgresql-13-13.13/doc/src/sgml/html/pgarchivecleanup.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgarchivecleanup.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/pgbench.html postgresql-13-13.14/doc/src/sgml/html/pgbench.html --- postgresql-13-13.13/doc/src/sgml/html/pgbench.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgbench.html 2024-02-05 22:04:24.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.13/doc/src/sgml/html/pgbuffercache.html postgresql-13-13.14/doc/src/sgml/html/pgbuffercache.html --- postgresql-13-13.13/doc/src/sgml/html/pgbuffercache.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgbuffercache.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgcrypto.html postgresql-13-13.14/doc/src/sgml/html/pgcrypto.html --- postgresql-13-13.13/doc/src/sgml/html/pgcrypto.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgcrypto.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgfreespacemap.html postgresql-13-13.14/doc/src/sgml/html/pgfreespacemap.html --- postgresql-13-13.13/doc/src/sgml/html/pgfreespacemap.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgfreespacemap.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgprewarm.html postgresql-13-13.14/doc/src/sgml/html/pgprewarm.html --- postgresql-13-13.13/doc/src/sgml/html/pgprewarm.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgprewarm.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgrowlocks.html postgresql-13-13.14/doc/src/sgml/html/pgrowlocks.html --- postgresql-13-13.13/doc/src/sgml/html/pgrowlocks.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgrowlocks.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgstandby.html postgresql-13-13.14/doc/src/sgml/html/pgstandby.html --- postgresql-13-13.13/doc/src/sgml/html/pgstandby.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgstandby.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgstatstatements.html postgresql-13-13.14/doc/src/sgml/html/pgstatstatements.html --- postgresql-13-13.13/doc/src/sgml/html/pgstatstatements.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgstatstatements.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgstattuple.html postgresql-13-13.14/doc/src/sgml/html/pgstattuple.html --- postgresql-13-13.13/doc/src/sgml/html/pgstattuple.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgstattuple.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgtestfsync.html postgresql-13-13.14/doc/src/sgml/html/pgtestfsync.html --- postgresql-13-13.13/doc/src/sgml/html/pgtestfsync.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgtestfsync.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/pgtesttiming.html postgresql-13-13.14/doc/src/sgml/html/pgtesttiming.html --- postgresql-13-13.13/doc/src/sgml/html/pgtesttiming.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgtesttiming.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/pgtrgm.html postgresql-13-13.14/doc/src/sgml/html/pgtrgm.html --- postgresql-13-13.13/doc/src/sgml/html/pgtrgm.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgtrgm.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgupgrade.html postgresql-13-13.14/doc/src/sgml/html/pgupgrade.html --- postgresql-13-13.13/doc/src/sgml/html/pgupgrade.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgupgrade.html 2024-02-05 22:04:25.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 @@ -425,4 +425,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.13/doc/src/sgml/html/pgvisibility.html postgresql-13-13.14/doc/src/sgml/html/pgvisibility.html --- postgresql-13-13.13/doc/src/sgml/html/pgvisibility.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgvisibility.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/pgwaldump.html postgresql-13-13.14/doc/src/sgml/html/pgwaldump.html --- postgresql-13-13.13/doc/src/sgml/html/pgwaldump.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgwaldump.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/pgxlogdump.html postgresql-13-13.14/doc/src/sgml/html/pgxlogdump.html --- postgresql-13-13.13/doc/src/sgml/html/pgxlogdump.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pgxlogdump.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/planner-optimizer.html postgresql-13-13.14/doc/src/sgml/html/planner-optimizer.html --- postgresql-13-13.13/doc/src/sgml/html/planner-optimizer.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/planner-optimizer.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/planner-stats-details.html postgresql-13-13.14/doc/src/sgml/html/planner-stats-details.html --- postgresql-13-13.13/doc/src/sgml/html/planner-stats-details.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/planner-stats-details.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/planner-stats-security.html postgresql-13-13.14/doc/src/sgml/html/planner-stats-security.html --- postgresql-13-13.13/doc/src/sgml/html/planner-stats-security.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/planner-stats-security.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/planner-stats.html postgresql-13-13.14/doc/src/sgml/html/planner-stats.html --- postgresql-13-13.13/doc/src/sgml/html/planner-stats.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/planner-stats.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/plhandler.html postgresql-13-13.14/doc/src/sgml/html/plhandler.html --- postgresql-13-13.13/doc/src/sgml/html/plhandler.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plhandler.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/plperl-builtins.html postgresql-13-13.14/doc/src/sgml/html/plperl-builtins.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-builtins.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-builtins.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-data.html postgresql-13-13.14/doc/src/sgml/html/plperl-data.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-data.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-data.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-event-triggers.html postgresql-13-13.14/doc/src/sgml/html/plperl-event-triggers.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-event-triggers.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-event-triggers.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-funcs.html postgresql-13-13.14/doc/src/sgml/html/plperl-funcs.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-funcs.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-funcs.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-global.html postgresql-13-13.14/doc/src/sgml/html/plperl-global.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-global.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-global.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-triggers.html postgresql-13-13.14/doc/src/sgml/html/plperl-triggers.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-triggers.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-triggers.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-trusted.html postgresql-13-13.14/doc/src/sgml/html/plperl-trusted.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-trusted.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-trusted.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl-under-the-hood.html postgresql-13-13.14/doc/src/sgml/html/plperl-under-the-hood.html --- postgresql-13-13.13/doc/src/sgml/html/plperl-under-the-hood.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl-under-the-hood.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plperl.html postgresql-13-13.14/doc/src/sgml/html/plperl.html --- postgresql-13-13.13/doc/src/sgml/html/plperl.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plperl.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-control-structures.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-control-structures.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-control-structures.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-control-structures.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-cursors.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-cursors.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-cursors.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-cursors.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-declarations.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-declarations.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-declarations.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-declarations.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-development-tips.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-development-tips.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-development-tips.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-development-tips.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-errors-and-messages.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-errors-and-messages.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-errors-and-messages.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-errors-and-messages.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-expressions.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-expressions.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-expressions.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-expressions.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-implementation.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-implementation.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-implementation.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-overview.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-overview.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-overview.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-overview.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-porting.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-porting.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-porting.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-porting.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-statements.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-statements.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-statements.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-statements.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-structure.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-structure.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-structure.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-structure.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-transactions.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-transactions.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-transactions.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-transactions.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql-trigger.html postgresql-13-13.14/doc/src/sgml/html/plpgsql-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql-trigger.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql-trigger.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpgsql.html postgresql-13-13.14/doc/src/sgml/html/plpgsql.html --- postgresql-13-13.13/doc/src/sgml/html/plpgsql.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpgsql.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-data.html postgresql-13-13.14/doc/src/sgml/html/plpython-data.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-data.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-data.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-database.html postgresql-13-13.14/doc/src/sgml/html/plpython-database.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-database.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-database.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-do.html postgresql-13-13.14/doc/src/sgml/html/plpython-do.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-do.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-do.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-envar.html postgresql-13-13.14/doc/src/sgml/html/plpython-envar.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-envar.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-envar.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-funcs.html postgresql-13-13.14/doc/src/sgml/html/plpython-funcs.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-funcs.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-funcs.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-python23.html postgresql-13-13.14/doc/src/sgml/html/plpython-python23.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-python23.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-python23.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-sharing.html postgresql-13-13.14/doc/src/sgml/html/plpython-sharing.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-sharing.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-sharing.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-subtransaction.html postgresql-13-13.14/doc/src/sgml/html/plpython-subtransaction.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-subtransaction.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-subtransaction.html 2024-02-05 22:04:16.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, @@ -52,7 +52,7 @@ plpy.execute(plan, [result]) $$ LANGUAGE plpythonu;

    - Note that the use of try/catch is still + Note that the use of try/except is still required. Otherwise the exception would propagate to the top of the Python stack and would cause the whole function to abort with a PostgreSQL error, so that the @@ -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.13/doc/src/sgml/html/plpython-transactions.html postgresql-13-13.14/doc/src/sgml/html/plpython-transactions.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-transactions.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-transactions.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-trigger.html postgresql-13-13.14/doc/src/sgml/html/plpython-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-trigger.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-trigger.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython-util.html postgresql-13-13.14/doc/src/sgml/html/plpython-util.html --- postgresql-13-13.13/doc/src/sgml/html/plpython-util.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython-util.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/plpython.html postgresql-13-13.14/doc/src/sgml/html/plpython.html --- postgresql-13-13.13/doc/src/sgml/html/plpython.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/plpython.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-config.html postgresql-13-13.14/doc/src/sgml/html/pltcl-config.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-config.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-config.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-data.html postgresql-13-13.14/doc/src/sgml/html/pltcl-data.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-data.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-data.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-dbaccess.html postgresql-13-13.14/doc/src/sgml/html/pltcl-dbaccess.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-dbaccess.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-dbaccess.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-error-handling.html postgresql-13-13.14/doc/src/sgml/html/pltcl-error-handling.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-error-handling.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-error-handling.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-event-trigger.html postgresql-13-13.14/doc/src/sgml/html/pltcl-event-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-event-trigger.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-event-trigger.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-functions.html postgresql-13-13.14/doc/src/sgml/html/pltcl-functions.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-functions.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-functions.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-global.html postgresql-13-13.14/doc/src/sgml/html/pltcl-global.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-global.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-global.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-overview.html postgresql-13-13.14/doc/src/sgml/html/pltcl-overview.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-overview.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-overview.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-procnames.html postgresql-13-13.14/doc/src/sgml/html/pltcl-procnames.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-procnames.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-procnames.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-subtransactions.html postgresql-13-13.14/doc/src/sgml/html/pltcl-subtransactions.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-subtransactions.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-subtransactions.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-transactions.html postgresql-13-13.14/doc/src/sgml/html/pltcl-transactions.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-transactions.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-transactions.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl-trigger.html postgresql-13-13.14/doc/src/sgml/html/pltcl-trigger.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl-trigger.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl-trigger.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/pltcl.html postgresql-13-13.14/doc/src/sgml/html/pltcl.html --- postgresql-13-13.13/doc/src/sgml/html/pltcl.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/pltcl.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/populate.html postgresql-13-13.14/doc/src/sgml/html/populate.html --- postgresql-13-13.13/doc/src/sgml/html/populate.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/populate.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/postgres-fdw.html postgresql-13-13.14/doc/src/sgml/html/postgres-fdw.html --- postgresql-13-13.13/doc/src/sgml/html/postgres-fdw.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/postgres-fdw.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/postgres-user.html postgresql-13-13.14/doc/src/sgml/html/postgres-user.html --- postgresql-13-13.13/doc/src/sgml/html/postgres-user.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/postgres-user.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/preface.html postgresql-13-13.14/doc/src/sgml/html/preface.html --- postgresql-13-13.13/doc/src/sgml/html/preface.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/preface.html 2024-02-05 22:04:04.000000000 +0000 @@ -1,5 +1,5 @@ -Preface
    Preface
    Prev UpPostgreSQL 13.13 DocumentationHome Next
    Prev Up Next
    PostgreSQL 13.13 Documentation Home 1.  What Is PostgreSQL?
    \ No newline at end of file +

    Prev Up Next
    PostgreSQL 13.14 Documentation Home 1.  What Is PostgreSQL?
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/preventing-server-spoofing.html postgresql-13-13.14/doc/src/sgml/html/preventing-server-spoofing.html --- postgresql-13-13.13/doc/src/sgml/html/preventing-server-spoofing.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/preventing-server-spoofing.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/progress-reporting.html postgresql-13-13.14/doc/src/sgml/html/progress-reporting.html --- postgresql-13-13.13/doc/src/sgml/html/progress-reporting.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/progress-reporting.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/protocol-changes.html postgresql-13-13.14/doc/src/sgml/html/protocol-changes.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-changes.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-changes.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-error-fields.html postgresql-13-13.14/doc/src/sgml/html/protocol-error-fields.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-error-fields.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-error-fields.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-flow.html postgresql-13-13.14/doc/src/sgml/html/protocol-flow.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-flow.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-flow.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-logical-replication.html postgresql-13-13.14/doc/src/sgml/html/protocol-logical-replication.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-logical-replication.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-logical-replication.html 2024-02-05 22:04:27.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 @@ -7,21 +7,26 @@

    The logical streaming replication protocol builds on the primitives of the physical streaming replication protocol. +

    + PostgreSQL logical decoding supports output + plugins. pgoutput is the standard one used for + the built-in logical replication.

    52.5.1. Logical Streaming Replication Parameters

    - The logical replication START_REPLICATION command - accepts following parameters: + Using the START_REPLICATION command, + pgoutput accepts the following options:

    proto_version

    Protocol version. Currently only version 1 is - supported. + supported. A valid version is required.

    publication_names

    Comma separated list of publication names for which to subscribe (receive changes). The individual publication names are treated as standard objects names and can be quoted the same as needed. + At least one publication name is required.

    52.5.2. Logical Replication Protocol Messages

    @@ -71,4 +76,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.13/doc/src/sgml/html/protocol-logicalrep-message-formats.html postgresql-13-13.14/doc/src/sgml/html/protocol-logicalrep-message-formats.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-logicalrep-message-formats.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-logicalrep-message-formats.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-message-formats.html postgresql-13-13.14/doc/src/sgml/html/protocol-message-formats.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-message-formats.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-message-formats.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-message-types.html postgresql-13-13.14/doc/src/sgml/html/protocol-message-types.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-message-types.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-message-types.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-overview.html postgresql-13-13.14/doc/src/sgml/html/protocol-overview.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-overview.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-overview.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/protocol-replication.html postgresql-13-13.14/doc/src/sgml/html/protocol-replication.html --- postgresql-13-13.13/doc/src/sgml/html/protocol-replication.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol-replication.html 2024-02-05 22:04:27.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, @@ -332,7 +332,10 @@

    XXX/XXX

    The WAL location to begin streaming at.

    option_name

    - The name of an option passed to the slot's logical decoding plugin. + The name of an option passed to the slot's logical decoding output + plugin. See Section 52.5 for + options that are accepted by the standard (pgoutput) + plugin.

    option_value

    Optional value, in the form of a string constant, associated with the specified option. @@ -497,4 +500,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.13/doc/src/sgml/html/protocol.html postgresql-13-13.14/doc/src/sgml/html/protocol.html --- postgresql-13-13.13/doc/src/sgml/html/protocol.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/protocol.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/queries-limit.html postgresql-13-13.14/doc/src/sgml/html/queries-limit.html --- postgresql-13-13.13/doc/src/sgml/html/queries-limit.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-limit.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries-order.html postgresql-13-13.14/doc/src/sgml/html/queries-order.html --- postgresql-13-13.13/doc/src/sgml/html/queries-order.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-order.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries-overview.html postgresql-13-13.14/doc/src/sgml/html/queries-overview.html --- postgresql-13-13.13/doc/src/sgml/html/queries-overview.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-overview.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries-select-lists.html postgresql-13-13.14/doc/src/sgml/html/queries-select-lists.html --- postgresql-13-13.13/doc/src/sgml/html/queries-select-lists.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-select-lists.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries-table-expressions.html postgresql-13-13.14/doc/src/sgml/html/queries-table-expressions.html --- postgresql-13-13.13/doc/src/sgml/html/queries-table-expressions.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-table-expressions.html 2024-02-05 22:04:05.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 @@ -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.13/doc/src/sgml/html/queries-union.html postgresql-13-13.14/doc/src/sgml/html/queries-union.html --- postgresql-13-13.13/doc/src/sgml/html/queries-union.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-union.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries-values.html postgresql-13-13.14/doc/src/sgml/html/queries-values.html --- postgresql-13-13.13/doc/src/sgml/html/queries-values.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-values.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries-with.html postgresql-13-13.14/doc/src/sgml/html/queries-with.html --- postgresql-13-13.13/doc/src/sgml/html/queries-with.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries-with.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/queries.html postgresql-13-13.14/doc/src/sgml/html/queries.html --- postgresql-13-13.13/doc/src/sgml/html/queries.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/queries.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/query-path.html postgresql-13-13.14/doc/src/sgml/html/query-path.html --- postgresql-13-13.13/doc/src/sgml/html/query-path.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/query-path.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/querytree.html postgresql-13-13.14/doc/src/sgml/html/querytree.html --- postgresql-13-13.13/doc/src/sgml/html/querytree.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/querytree.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rangetypes.html postgresql-13-13.14/doc/src/sgml/html/rangetypes.html --- postgresql-13-13.13/doc/src/sgml/html/rangetypes.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rangetypes.html 2024-02-05 22:04:06.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.13/doc/src/sgml/html/recovery-config.html postgresql-13-13.14/doc/src/sgml/html/recovery-config.html --- postgresql-13-13.13/doc/src/sgml/html/recovery-config.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/recovery-config.html 2024-02-05 22:04:34.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.13/doc/src/sgml/html/reference-client.html postgresql-13-13.14/doc/src/sgml/html/reference-client.html --- postgresql-13-13.13/doc/src/sgml/html/reference-client.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/reference-client.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/reference-server.html postgresql-13-13.14/doc/src/sgml/html/reference-server.html --- postgresql-13-13.13/doc/src/sgml/html/reference-server.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/reference-server.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/reference.html postgresql-13-13.14/doc/src/sgml/html/reference.html --- postgresql-13-13.13/doc/src/sgml/html/reference.html 2023-11-06 22:30:46.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/reference.html 2024-02-05 22:04:25.000000000 +0000 @@ -1,5 +1,5 @@ -Part VI. Reference
    Part VI. Reference
    Prev UpPostgreSQL 13.13 DocumentationHome Next

    Part VI. Reference

    +Part VI. Reference

    Part VI. Reference
    Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/regress-coverage.html postgresql-13-13.14/doc/src/sgml/html/regress-coverage.html --- postgresql-13-13.13/doc/src/sgml/html/regress-coverage.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/regress-coverage.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/regress-evaluation.html postgresql-13-13.14/doc/src/sgml/html/regress-evaluation.html --- postgresql-13-13.13/doc/src/sgml/html/regress-evaluation.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/regress-evaluation.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/regress-run.html postgresql-13-13.14/doc/src/sgml/html/regress-run.html --- postgresql-13-13.13/doc/src/sgml/html/regress-run.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/regress-run.html 2024-02-05 22:04:12.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 @@ -268,4 +268,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.13/doc/src/sgml/html/regress-tap.html postgresql-13-13.14/doc/src/sgml/html/regress-tap.html --- postgresql-13-13.13/doc/src/sgml/html/regress-tap.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/regress-tap.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/regress-variant.html postgresql-13-13.14/doc/src/sgml/html/regress-variant.html --- postgresql-13-13.13/doc/src/sgml/html/regress-variant.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/regress-variant.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/regress.html postgresql-13-13.14/doc/src/sgml/html/regress.html --- postgresql-13-13.13/doc/src/sgml/html/regress.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/regress.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/release-13-1.html postgresql-13-13.14/doc/src/sgml/html/release-13-1.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-1.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-1.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,11 +1,11 @@ -E.13. Release 13.1
    E.13. Release 13.1
    Prev UpAppendix E. Release NotesHome Next

    E.13. Release 13.1

    E.13.1. Migration to Version 13.1
    E.13.2. Changes

    Release date: 2020-11-12

    +E.14. Release 13.1

    E.14. Release 13.1
    Prev UpAppendix E. Release NotesHome Next

    E.14. Release 13.1

    E.14.1. Migration to Version 13.1
    E.14.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.14. -

    E.13.1. Migration to Version 13.1

    + Section E.15. +

    E.14.1. Migration to Version 13.1

    A dump/restore is not required for those running 13.X. -

    E.13.2. Changes

    • +

    E.14.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.12. Release 13.2 Home E.14. Release 13
    \ No newline at end of file +

    Prev Up Next
    E.13. Release 13.2 Home E.15. Release 13
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-10.html postgresql-13-13.14/doc/src/sgml/html/release-13-10.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-10.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-10.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,14 +1,14 @@ -E.4. Release 13.10
    E.4. Release 13.10
    Prev UpAppendix E. Release NotesHome Next

    E.4. Release 13.10

    E.4.1. Migration to Version 13.10
    E.4.2. Changes

    Release date: 2023-02-09

    +E.5. Release 13.10

    E.5. Release 13.10
    Prev UpAppendix E. Release NotesHome Next

    E.5. Release 13.10

    E.5.1. Migration to Version 13.10
    E.5.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.14. -

    E.4.1. Migration to Version 13.10

    + Section E.15. +

    E.5.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.7. -

    E.4.2. Changes

    E.5.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.3. Release 13.11 Home E.5. Release 13.9
    \ No newline at end of file +

    Prev Up Next
    E.4. Release 13.11 Home E.6. Release 13.9
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-11.html postgresql-13-13.14/doc/src/sgml/html/release-13-11.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-11.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-11.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,14 +1,14 @@ -E.3. Release 13.11
    E.3. Release 13.11
    Prev UpAppendix E. Release NotesHome Next

    E.3. Release 13.11

    E.3.1. Migration to Version 13.11
    E.3.2. Changes

    Release date: 2023-05-11

    +E.4. Release 13.11

    E.4. Release 13.11
    Prev UpAppendix E. Release NotesHome Next

    E.4. Release 13.11

    E.4.1. Migration to Version 13.11
    E.4.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.14. -

    E.3.1. Migration to Version 13.11

    + Section E.15. +

    E.4.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.7. -

    E.3.2. Changes

    E.4.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
    E.2. Release 13.12 Home E.4. Release 13.10
    \ No newline at end of file +

    Prev Up Next
    E.3. Release 13.12 Home E.5. Release 13.10
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-12.html postgresql-13-13.14/doc/src/sgml/html/release-13-12.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-12.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-12.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,24 +1,24 @@ -E.2. Release 13.12
    E.2. Release 13.12
    Prev UpAppendix E. Release NotesHome Next

    E.2. Release 13.12

    E.2.1. Migration to Version 13.12
    E.2.2. Changes

    Release date: 2023-08-10

    +E.3. Release 13.12

    E.3. Release 13.12
    Prev UpAppendix E. Release NotesHome Next

    E.3. Release 13.12

    E.3.1. Migration to Version 13.12
    E.3.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.14. -

    E.2.1. Migration to Version 13.12

    + Section E.15. +

    E.3.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.7. -

    E.2.2. Changes

    E.3.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, + The PostgreSQL Project thanks Micah Gates, Valerie Woolard, Tim Carey-Smith, and Christoph Berg for reporting this problem. (CVE-2023-39417) @@ -264,4 +264,4 @@

    • Silence deprecation warnings when compiling with OpenSSL 3.0.0 or later (Peter Eisentraut) -

    Prev Up Next
    E.1. Release 13.13 Home E.3. Release 13.11
    \ No newline at end of file +

    Prev Up Next
    E.2. Release 13.13 Home E.4. Release 13.11
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-13.html postgresql-13-13.14/doc/src/sgml/html/release-13-13.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-13.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-13.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,9 +1,9 @@ -E.1. Release 13.13
    E.1. Release 13.13
    Prev UpAppendix E. Release NotesHome Next

    E.1. Release 13.13

    E.1.1. Migration to Version 13.13
    E.1.2. Changes

    Release date: 2023-11-09

    +E.2. Release 13.13

    E.2. Release 13.13
    Prev UpAppendix E. Release NotesHome Next

    E.2. Release 13.13

    E.2.1. Migration to Version 13.13
    E.2.2. Changes

    Release date: 2023-11-09

    This release contains a variety of fixes from 13.12. For information about new features in major release 13, see - Section E.14. -

    E.1.1. Migration to Version 13.13

    + Section E.15. +

    E.2.1. Migration to Version 13.13

    A dump/restore is not required for those running 13.X.

    However, several mistakes have been discovered that could lead to @@ -14,8 +14,8 @@ entries below.

    Also, if you are upgrading from a version earlier than 13.12, - see Section E.2. -

    E.1.2. Changes

    E.2.2. Changes

    • Fix handling of unknown-type arguments in DISTINCT "any" aggregate functions (Tom Lane) @@ -371,4 +371,4 @@ abbreviation for a zone with a total human population of about two dozen, it seems unlikely that anyone will miss it. If someone does, they can put it back via a custom abbreviations file. -

    Prev Up Next
    Appendix E. Release Notes Home E.2. Release 13.12
    \ No newline at end of file +

    Prev Up Next
    E.1. Release 13.14 Home E.3. Release 13.12
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-14.html postgresql-13-13.14/doc/src/sgml/html/release-13-14.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-14.html 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-14.html 2024-02-05 22:04:31.000000000 +0000 @@ -0,0 +1,302 @@ + +E.1. Release 13.14
    E.1. Release 13.14
    Prev UpAppendix E. Release NotesHome Next

    E.1. Release 13.14

    E.1.1. Migration to Version 13.14
    E.1.2. Changes

    Release date: 2024-02-08

    + This release contains a variety of fixes from 13.13. + For information about new features in major release 13, see + Section E.15. +

    E.1.1. Migration to Version 13.14

    + A dump/restore is not required for those running 13.X. +

    + However, one bug was fixed that could have resulted in corruption of + GIN indexes during concurrent updates. If you suspect such + corruption, reindex affected indexes after installing this update. +

    + Also, if you are upgrading from a version earlier than 13.13, + see Section E.2. +

    E.1.2. Changes

    • + Tighten security restrictions within REFRESH MATERIALIZED + VIEW CONCURRENTLY (Heikki Linnakangas) +

      + One step of a concurrent refresh command was run under weak security + restrictions. If a materialized view's owner could persuade a + superuser or other high-privileged user to perform a concurrent + refresh on that view, the view's owner could control code executed + with the privileges of the user running REFRESH. + Fix things so that all user-determined code is run as the view's + owner, as expected. +

      + The only known exploit for this error does not work + in PostgreSQL 16.0 and later, so it may + be that v16 is not vulnerable in practice. +

      + The PostgreSQL Project thanks Pedro + Gallegos for reporting this problem. + (CVE-2024-0985) +

    • + Fix memory leak when performing JIT inlining (Andres Freund, + Daniel Gustafsson) +

      + There have been multiple reports of backend processes suffering + out-of-memory conditions after sufficiently many JIT compilations. + This fix should resolve that. +

    • + When dequeueing from an LWLock, avoid needing to search the list of + waiting processes (Andres Freund) +

      + This fixes O(N^2) behavior when the list of waiters is long. In + some use-cases this results in substantial throughput improvements. +

    • + Avoid generating incorrect partitioned-join plans (Richard Guo) +

      + Some uncommon situations involving lateral references could create + incorrect plans. Affected queries could produce wrong answers, or + odd failures such as “variable not found in subplan target + list”, or executor crashes. +

    • + Fix incorrect wrapping of subquery output expressions in + PlaceHolderVars (Tom Lane) +

      + This fixes incorrect results when a subquery is underneath an outer + join and has an output column that laterally references something + outside the outer join's scope. The output column might not appear + as NULL when it should do so due to the action of the outer join. +

    • + Avoid requesting an oversize shared-memory area in parallel hash + join (Thomas Munro, Andrei Lepikhov, Alexander Korotkov) +

      + The limiting value was too large, allowing “invalid DSA memory + alloc request size” errors to occur with sufficiently large + expected hash table sizes. +

    • + Avoid assertion failures in heap_update() + and heap_delete() when a tuple to be updated by + a foreign-key enforcement trigger fails the extra visibility + crosscheck (Alexander Lakhin) +

      + This error had no impact in non-assert builds. +

    • + Fix possible failure during ALTER TABLE ADD + COLUMN on a complex inheritance tree (Tender Wang) +

      + If a grandchild table would inherit the new column via multiple + intermediate parents, the command failed with “tuple already + updated by self”. +

    • + Fix problems with duplicate token names in ALTER TEXT + SEARCH CONFIGURATION ... MAPPING commands (Tender Wang, + Michael Paquier) +

    • + Properly lock the associated table during DROP + STATISTICS (Tomas Vondra) +

      + Failure to acquire the lock could result in “tuple + concurrently deleted” errors if the DROP + executes concurrently with ANALYZE. +

    • + Fix function volatility checking for GENERATED + and DEFAULT expressions (Tom Lane) +

      + These places could fail to detect insertion of a volatile function + default-argument expression, or decide that a polymorphic function + is volatile although it is actually immutable on the datatype of + interest. This could lead to improperly rejecting or accepting + a GENERATED clause, or to mistakenly applying the + constant-default-value optimization in ALTER TABLE ADD + COLUMN. +

    • + Detect that a new catalog cache entry became stale while detoasting + its fields (Tom Lane) +

      + We expand any out-of-line fields in a catalog tuple before inserting + it into the catalog caches. That involves database access which + might cause invalidation of catalog cache entries — but the + new entry isn't in the cache yet, so we would miss noticing that it + should get invalidated. The result is a race condition in which an + already-stale cache entry could get made, and then persist + indefinitely. This would lead to hard-to-predict misbehavior. + Fix by rechecking the tuple's visibility after detoasting. +

    • + Fix edge-case integer overflow detection bug on some platforms (Dean + Rasheed) +

      + Computing 0 - INT64_MIN should result in an + overflow error, and did on most platforms. However, platforms with + neither integer overflow builtins nor 128-bit integers would fail to + spot the overflow, instead returning INT64_MIN. +

    • + Detect Julian-date overflow when adding or subtracting + an interval to/from a timestamp (Tom Lane) +

      + Some cases that should cause an out-of-range error produced an + incorrect result instead. +

    • + Add more checks for overflow in interval_mul() + and interval_div() (Dean Rasheed) +

      + Some cases that should cause an out-of-range error produced an + incorrect result instead. +

    • + Make the pg_file_settings view check + validity of unapplied values for settings + with backend + or superuser-backend context (Tom Lane) +

      + Invalid values were not noted in the view as intended. This escaped + detection because there are very few settings in these groups. +

    • + Match collation too when matching an existing index to a new + partitioned index (Peter Eisentraut) +

      + Previously we could accept an index that has a different collation + from the corresponding element of the partition key, possibly + leading to misbehavior. +

    • + Fix insufficient locking when cleaning up an incomplete split of + a GIN index's internal page (Fei Changhong, Heikki Linnakangas) +

      + The code tried to do this with shared rather than exclusive lock on + the buffer. This could lead to index corruption if two processes + attempted the cleanup concurrently. +

    • + Avoid premature release of buffer pin in GIN index insertion + (Tom Lane) +

      + If an index root page split occurs concurrently with our own + insertion, the code could fail with “buffer NNNN is not owned + by resource owner”. +

    • + Avoid failure with partitioned SP-GiST indexes (Tom Lane) +

      + Trying to use an index of this kind could lead to “No such + file or directory” errors. +

    • + Fix ownership change reporting for large objects (Tom Lane) +

      + A no-op ALTER LARGE OBJECT OWNER command (that + is, one selecting the existing owner) passed the wrong class ID to + the PostAlterHook, probably confusing any + extension using that hook. +

    • + Prevent standby servers from incorrectly processing dead index + tuples during subtransactions (Fei Changhong) +

      + The startedInRecovery flag was not + correctly set for a subtransaction. This affects only processing of + dead index tuples. It could allow a query in a subtransaction to + ignore index entries that it should return (if they are already dead + on the primary server, but not dead to the standby transaction), or + to prematurely mark index entries as dead that are not yet dead on + the primary. It is not clear that the latter case has any serious + consequences, but it's not the intended behavior. +

    • + Fix deadlock between a logical replication apply worker, its + tablesync worker, and a session process trying to alter the + subscription (Shlok Kyal) +

      + One edge of the deadlock loop did not involve a lock wait, so the + deadlock went undetected and would persist until manual + intervention. +

    • + Return the correct status code when a new client disconnects without + responding to the server's password challenge (Liu Lang, Tom Lane) +

      + In some cases we'd treat this as a loggable error, which was not the + intention and tends to create log spam, since common clients + like psql frequently do this. It may + also confuse extensions that + use ClientAuthentication_hook. +

    • + Fix incompatibility with OpenSSL 3.2 + (Tristan Partin, Bo Andreson) +

      + Use the BIO “app_data” field for our private storage, + instead of assuming it's okay to use the “data” field. + This mistake didn't cause problems before, but with 3.2 it leads + to crashes and complaints about double frees. +

    • + Be more wary about OpenSSL not + setting errno on error (Tom Lane) +

      + If errno isn't set, assume the cause of the + reported failure is read EOF. This fixes rare cases of strange + error reports like “could not accept SSL connection: + Success”. +

    • + Report ENOMEM errors from file-related system + calls as ERRCODE_OUT_OF_MEMORY, + not ERRCODE_INTERNAL_ERROR (Alexander Kuzmenkov) +

    • + Avoid race condition when libpq + initializes OpenSSL support concurrently in two different threads + (Willi Mann, Michael Paquier) +

    • + Fix timing-dependent failure in GSSAPI data transmission (Tom Lane) +

      + When using GSSAPI encryption in non-blocking + mode, libpq sometimes failed + with “GSSAPI caller failed to retransmit all data needing to + be retried”. +

    • + In pg_dump, don't dump RLS policies or + security labels for extension member objects (Tom Lane, Jacob + Champion) +

      + Previously, commands would be included in the dump to set these + properties, which is really incorrect since they should be + considered as internal affairs of the extension. Moreover, the + restoring user might not have adequate privilege to set them, and + indeed the dumping user might not have enough privilege to dump them + (since dumping RLS policies requires acquiring lock on their table). +

    • + In pg_dump, don't dump an extended + statistics object if its underlying table isn't being dumped + (Rian McGuire, Tom Lane) +

      + This conforms to the behavior for other dependent objects such as + indexes. +

    • + Fix crash in contrib/intarray if an array with + an element equal to INT_MAX is inserted into + a gist__int_ops index + (Alexander Lakhin, Tom Lane) +

    • + Report a better error + when contrib/pageinspect's + hash_bitmap_info() function is applied to a + partitioned hash index (Alexander Lakhin, Michael Paquier) +

    • + Report a better error + when contrib/pgstattuple's + pgstathashindex() function is applied to a + partitioned hash index (Alexander Lakhin) +

    • + On Windows, suppress autorun options when launching subprocesses + in pg_ctl + and pg_regress (Kyotaro Horiguchi) +

      + When launching a child process via cmd.exe, + pass the /D flag to prevent executing any autorun + commands specified in the registry. This avoids possibly-surprising + side effects. +

    • + Fix compilation failures with libxml2 + version 2.12.0 and later (Tom Lane) +

    • + Fix compilation failure of WAL_DEBUG code on + Windows (Bharath Rupireddy) +

    • + Suppress compiler warnings from Python's header files + (Peter Eisentraut, Tom Lane) +

      + Our preferred compiler options provoke warnings about constructs + appearing in recent versions of Python's header files. When using + gcc, we can suppress these warnings with + a pragma. +

    • + Avoid deprecation warning when compiling with LLVM 18 (Thomas Munro) +

    • + Update time zone data files to tzdata + release 2024a for DST law changes in Greenland, Kazakhstan, and + Palestine, plus corrections for the Antarctic stations Casey and + Vostok. Also historical corrections for Vietnam, Toronto, and + Miquelon. +

    Prev Up Next
    Appendix E. Release Notes Home E.2. Release 13.13
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-2.html postgresql-13-13.14/doc/src/sgml/html/release-13-2.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-2.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-2.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,16 +1,16 @@ -E.12. Release 13.2
    E.12. Release 13.2
    Prev UpAppendix E. Release NotesHome Next

    E.12. Release 13.2

    E.12.1. Migration to Version 13.2
    E.12.2. Changes

    Release date: 2021-02-11

    +E.13. Release 13.2

    E.13. Release 13.2
    Prev UpAppendix E. Release NotesHome Next

    E.13. Release 13.2

    E.13.1. Migration to Version 13.2
    E.13.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.14. -

    E.12.1. Migration to Version 13.2

    + Section E.15. +

    E.13.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.12.2. Changes

    • +

    E.13.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.11. Release 13.3 Home E.13. Release 13.1
    \ No newline at end of file +

    Prev Up Next
    E.12. Release 13.3 Home E.14. Release 13.1
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-3.html postgresql-13-13.14/doc/src/sgml/html/release-13-3.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-3.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-3.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,14 +1,14 @@ -E.11. Release 13.3
    E.11. Release 13.3
    Prev UpAppendix E. Release NotesHome Next

    E.11. Release 13.3

    E.11.1. Migration to Version 13.3
    E.11.2. Changes

    Release date: 2021-05-13

    +E.12. Release 13.3

    E.12. Release 13.3
    Prev UpAppendix E. Release NotesHome Next

    E.12. Release 13.3

    E.12.1. Migration to Version 13.3
    E.12.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.14. -

    E.11.1. Migration to Version 13.3

    + Section E.15. +

    E.12.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.12. -

    E.11.2. Changes

    E.12.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.10. Release 13.4 Home E.12. Release 13.2
    \ No newline at end of file +

    Prev Up Next
    E.11. Release 13.4 Home E.13. Release 13.2
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-4.html postgresql-13-13.14/doc/src/sgml/html/release-13-4.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-4.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-4.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,14 +1,14 @@ -E.10. Release 13.4
    E.10. Release 13.4
    Prev UpAppendix E. Release NotesHome Next

    E.10. Release 13.4

    E.10.1. Migration to Version 13.4
    E.10.2. Changes

    Release date: 2021-08-12

    +E.11. Release 13.4

    E.11. Release 13.4
    Prev UpAppendix E. Release NotesHome Next

    E.11. Release 13.4

    E.11.1. Migration to Version 13.4
    E.11.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.14. -

    E.10.1. Migration to Version 13.4

    + Section E.15. +

    E.11.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.12. -

    E.10.2. Changes

    E.11.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.9. Release 13.5 Home E.11. Release 13.3
    \ No newline at end of file +

    Prev Up Next
    E.10. Release 13.5 Home E.12. Release 13.3
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-5.html postgresql-13-13.14/doc/src/sgml/html/release-13-5.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-5.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-5.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,9 +1,9 @@ -E.9. Release 13.5
    E.9. Release 13.5
    Prev UpAppendix E. Release NotesHome Next

    E.9. Release 13.5

    E.9.1. Migration to Version 13.5
    E.9.2. Changes

    Release date: 2021-11-11

    +E.10. Release 13.5

    E.10. Release 13.5
    Prev UpAppendix E. Release NotesHome Next

    E.10. Release 13.5

    E.10.1. Migration to Version 13.5
    E.10.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.14. -

    E.9.1. Migration to Version 13.5

    + Section E.15. +

    E.10.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.12. -

    E.9.2. Changes

    E.10.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.8. Release 13.6 Home E.10. Release 13.4
    \ No newline at end of file +

    Prev Up Next
    E.9. Release 13.6 Home E.11. Release 13.4
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-6.html postgresql-13-13.14/doc/src/sgml/html/release-13-6.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-6.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-6.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,9 +1,9 @@ -E.8. Release 13.6
    E.8. Release 13.6
    Prev UpAppendix E. Release NotesHome Next

    E.8. Release 13.6

    E.8.1. Migration to Version 13.6
    E.8.2. Changes

    Release date: 2022-02-10

    +E.9. Release 13.6

    E.9. Release 13.6
    Prev UpAppendix E. Release NotesHome Next

    E.9. Release 13.6

    E.9.1. Migration to Version 13.6
    E.9.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.14. -

    E.8.1. Migration to Version 13.6

    + Section E.15. +

    E.9.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.9. -

    E.8.2. Changes

    E.9.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.7. Release 13.7 Home E.9. Release 13.5
    \ No newline at end of file +

    Prev Up Next
    E.8. Release 13.7 Home E.10. Release 13.5
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-7.html postgresql-13-13.14/doc/src/sgml/html/release-13-7.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-7.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-7.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,9 +1,9 @@ -E.7. Release 13.7
    E.7. Release 13.7
    Prev UpAppendix E. Release NotesHome Next

    E.7. Release 13.7

    E.7.1. Migration to Version 13.7
    E.7.2. Changes

    Release date: 2022-05-12

    +E.8. Release 13.7

    E.8. Release 13.7
    Prev UpAppendix E. Release NotesHome Next

    E.8. Release 13.7

    E.8.1. Migration to Version 13.7
    E.8.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.14. -

    E.7.1. Migration to Version 13.7

    + Section E.15. +

    E.8.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.8. -

    E.7.2. Changes

    E.8.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.6. Release 13.8 Home E.8. Release 13.6
    \ No newline at end of file +

    Prev Up Next
    E.7. Release 13.8 Home E.9. Release 13.6
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-8.html postgresql-13-13.14/doc/src/sgml/html/release-13-8.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-8.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-8.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,14 +1,14 @@ -E.6. Release 13.8
    E.6. Release 13.8
    Prev UpAppendix E. Release NotesHome Next

    E.6. Release 13.8

    E.6.1. Migration to Version 13.8
    E.6.2. Changes

    Release date: 2022-08-11

    +E.7. Release 13.8

    E.7. Release 13.8
    Prev UpAppendix E. Release NotesHome Next

    E.7. Release 13.8

    E.7.1. Migration to Version 13.8
    E.7.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.14. -

    E.6.1. Migration to Version 13.8

    + Section E.15. +

    E.7.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.7. -

    E.6.2. Changes

    E.7.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.5. Release 13.9 Home E.7. Release 13.7
    \ No newline at end of file +

    Prev Up Next
    E.6. Release 13.9 Home E.8. Release 13.7
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13-9.html postgresql-13-13.14/doc/src/sgml/html/release-13-9.html --- postgresql-13-13.13/doc/src/sgml/html/release-13-9.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13-9.html 2024-02-05 22:04:31.000000000 +0000 @@ -1,14 +1,14 @@ -E.5. Release 13.9
    E.5. Release 13.9
    Prev UpAppendix E. Release NotesHome Next

    E.5. Release 13.9

    E.5.1. Migration to Version 13.9
    E.5.2. Changes

    Release date: 2022-11-10

    +E.6. Release 13.9

    E.6. Release 13.9
    Prev UpAppendix E. Release NotesHome Next

    E.6. Release 13.9

    E.6.1. Migration to Version 13.9
    E.6.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.14. -

    E.5.1. Migration to Version 13.9

    + Section E.15. +

    E.6.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.7. -

    E.5.2. Changes

    E.6.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.4. Release 13.10 Home E.6. Release 13.8
    \ No newline at end of file +

    Prev Up Next
    E.5. Release 13.10 Home E.7. Release 13.8
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-13.html postgresql-13-13.14/doc/src/sgml/html/release-13.html --- postgresql-13-13.13/doc/src/sgml/html/release-13.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-13.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,5 +1,5 @@ -E.14. Release 13
    E.14. Release 13
    Prev UpAppendix E. Release NotesHome Next

    E.14. Release 13

    E.14.1. Overview
    E.14.2. Migration to Version 13
    E.14.3. Changes
    E.14.4. Acknowledgments

    Release date: 2020-09-24

    E.14.1. Overview

    +E.15. Release 13

    E.15. Release 13
    Prev UpAppendix E. Release NotesHome Next

    E.15. Release 13

    E.15.1. Overview
    E.15.2. Migration to Version 13
    E.15.3. Changes
    E.15.4. Acknowledgments

    Release date: 2020-09-24

    E.15.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.14.2. Migration to Version 13

    +

    E.15.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.14.3. Changes

    +

    E.15.3. Changes

    Below you will find a detailed account of the changes between PostgreSQL 13 and the previous major release. -

    E.14.3.1. Server

    E.14.3.1.1. Partitioning

    • +

      E.15.3.1. Server

      E.15.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.14.3.1.2. Indexes

      • +

      E.15.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.14.3.1.3. Optimizer

      • +

      E.15.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.14.3.1.4. General Performance

      • +

      E.15.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.14.3.1.5. Monitoring

      • +

      E.15.3.1.5. Monitoring
      E.14.3.1.6. System Views

      • +

      E.15.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.14.3.1.7. Wait Events

      • +

      E.15.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.14.3.1.8. Authentication

      • +

      E.15.3.1.8. Authentication
      E.14.3.1.9. Server Configuration

      • +

      E.15.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.14.3.2. Streaming Replication and Recovery

      • +

    E.15.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.14.3.3. Utility Commands

    • +

    E.15.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.14.3.4. Data Types

    • +

    E.15.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.14.3.5. Functions

    • +

    E.15.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.14.3.6. PL/pgSQL

    • +

    E.15.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.14.3.7. Client Interfaces

    • +

    E.15.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.14.3.8. Client Applications

    E.14.3.8.1. psql

    • +

    E.15.3.8. Client Applications

    E.15.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.14.3.8.2. pgbench

    • +

    E.15.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.14.3.9. Server Applications

    • +

    E.15.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.14.3.10. Documentation

    • +

    E.15.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.14.3.11. Source Code

    • +

    E.15.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.14.3.12. Additional Modules

    • +

    E.15.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.14.4. Acknowledgments

    +

    E.15.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.13. Release 13.1 Home E.15. 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.14. Release 13.1 Home E.16. Prior Releases
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release-prior.html postgresql-13-13.14/doc/src/sgml/html/release-prior.html --- postgresql-13-13.13/doc/src/sgml/html/release-prior.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release-prior.html 2024-02-05 22:04:32.000000000 +0000 @@ -1,5 +1,5 @@ -E.15. Prior Releases
    E.15. Prior Releases
    Prev UpAppendix E. Release NotesHome Next

    E.15. Prior Releases

    +E.16. Prior Releases

    E.16. Prior Releases
    Prev UpAppendix E. Release NotesHome Next

    E.16. Prior Releases

    Release notes for prior release branches can be found at https://www.postgresql.org/docs/release/ -

    Prev Up Next
    E.14. Release 13 Home Appendix F. Additional Supplied Modules
    \ No newline at end of file +

    Prev Up Next
    E.15. Release 13 Home Appendix F. Additional Supplied Modules
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/release.html postgresql-13-13.14/doc/src/sgml/html/release.html --- postgresql-13-13.13/doc/src/sgml/html/release.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/release.html 2024-02-05 22:04:32.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.13
    E.1.1. Migration to Version 13.13
    E.1.2. Changes
    E.2. Release 13.12
    E.2.1. Migration to Version 13.12
    E.2.2. Changes
    E.3. Release 13.11
    E.3.1. Migration to Version 13.11
    E.3.2. Changes
    E.4. Release 13.10
    E.4.1. Migration to Version 13.10
    E.4.2. Changes
    E.5. Release 13.9
    E.5.1. Migration to Version 13.9
    E.5.2. Changes
    E.6. Release 13.8
    E.6.1. Migration to Version 13.8
    E.6.2. Changes
    E.7. Release 13.7
    E.7.1. Migration to Version 13.7
    E.7.2. Changes
    E.8. Release 13.6
    E.8.1. Migration to Version 13.6
    E.8.2. Changes
    E.9. Release 13.5
    E.9.1. Migration to Version 13.5
    E.9.2. Changes
    E.10. Release 13.4
    E.10.1. Migration to Version 13.4
    E.10.2. Changes
    E.11. Release 13.3
    E.11.1. Migration to Version 13.3
    E.11.2. Changes
    E.12. Release 13.2
    E.12.1. Migration to Version 13.2
    E.12.2. Changes
    E.13. Release 13.1
    E.13.1. Migration to Version 13.1
    E.13.2. Changes
    E.14. Release 13
    E.14.1. Overview
    E.14.2. Migration to Version 13
    E.14.3. Changes
    E.14.4. Acknowledgments
    E.15. 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.13
    \ No newline at end of file +

    Prev Up Next
    D.3. XML Limits and Conformance to SQL/XML Home E.1. Release 13.14
    \ No newline at end of file diff -Nru postgresql-13-13.13/doc/src/sgml/html/replication-origins.html postgresql-13-13.14/doc/src/sgml/html/replication-origins.html --- postgresql-13-13.13/doc/src/sgml/html/replication-origins.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/replication-origins.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/resources.html postgresql-13-13.14/doc/src/sgml/html/resources.html --- postgresql-13-13.13/doc/src/sgml/html/resources.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/resources.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/role-attributes.html postgresql-13-13.14/doc/src/sgml/html/role-attributes.html --- postgresql-13-13.13/doc/src/sgml/html/role-attributes.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/role-attributes.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/role-membership.html postgresql-13-13.14/doc/src/sgml/html/role-membership.html --- postgresql-13-13.13/doc/src/sgml/html/role-membership.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/role-membership.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/role-removal.html postgresql-13-13.14/doc/src/sgml/html/role-removal.html --- postgresql-13-13.13/doc/src/sgml/html/role-removal.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/role-removal.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/routine-reindex.html postgresql-13-13.14/doc/src/sgml/html/routine-reindex.html --- postgresql-13-13.13/doc/src/sgml/html/routine-reindex.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/routine-reindex.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/routine-vacuuming.html postgresql-13-13.14/doc/src/sgml/html/routine-vacuuming.html --- postgresql-13-13.13/doc/src/sgml/html/routine-vacuuming.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/routine-vacuuming.html 2024-02-05 22:04:11.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 @@ -632,4 +632,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.13/doc/src/sgml/html/row-estimation-examples.html postgresql-13-13.14/doc/src/sgml/html/row-estimation-examples.html --- postgresql-13-13.13/doc/src/sgml/html/row-estimation-examples.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/row-estimation-examples.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/rowtypes.html postgresql-13-13.14/doc/src/sgml/html/rowtypes.html --- postgresql-13-13.13/doc/src/sgml/html/rowtypes.html 2023-11-06 22:30:26.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rowtypes.html 2024-02-05 22:04:05.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.13/doc/src/sgml/html/rule-system.html postgresql-13-13.14/doc/src/sgml/html/rule-system.html --- postgresql-13-13.13/doc/src/sgml/html/rule-system.html 2023-11-06 22:30:47.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rule-system.html 2024-02-05 22:04:25.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.13/doc/src/sgml/html/rules-materializedviews.html postgresql-13-13.14/doc/src/sgml/html/rules-materializedviews.html --- postgresql-13-13.13/doc/src/sgml/html/rules-materializedviews.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules-materializedviews.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rules-privileges.html postgresql-13-13.14/doc/src/sgml/html/rules-privileges.html --- postgresql-13-13.13/doc/src/sgml/html/rules-privileges.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules-privileges.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rules-status.html postgresql-13-13.14/doc/src/sgml/html/rules-status.html --- postgresql-13-13.13/doc/src/sgml/html/rules-status.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules-status.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rules-triggers.html postgresql-13-13.14/doc/src/sgml/html/rules-triggers.html --- postgresql-13-13.13/doc/src/sgml/html/rules-triggers.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules-triggers.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rules-update.html postgresql-13-13.14/doc/src/sgml/html/rules-update.html --- postgresql-13-13.13/doc/src/sgml/html/rules-update.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules-update.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rules-views.html postgresql-13-13.14/doc/src/sgml/html/rules-views.html --- postgresql-13-13.13/doc/src/sgml/html/rules-views.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules-views.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/rules.html postgresql-13-13.14/doc/src/sgml/html/rules.html --- postgresql-13-13.13/doc/src/sgml/html/rules.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/rules.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/runtime-config-autovacuum.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-autovacuum.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-autovacuum.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-autovacuum.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-client.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-client.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-client.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-client.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-compatible.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-compatible.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-compatible.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-compatible.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-connection.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-connection.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-connection.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-connection.html 2024-02-05 22:04:10.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 @@ -473,4 +473,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.13/doc/src/sgml/html/runtime-config-custom.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-custom.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-custom.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-custom.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-developer.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-developer.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-developer.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-developer.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-error-handling.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-error-handling.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-error-handling.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-error-handling.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-file-locations.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-file-locations.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-file-locations.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-file-locations.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-locks.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-locks.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-locks.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-locks.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-logging.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-logging.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-logging.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-logging.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-preset.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-preset.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-preset.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-preset.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-query.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-query.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-query.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-query.html 2024-02-05 22:04:10.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 @@ -558,4 +558,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.13/doc/src/sgml/html/runtime-config-replication.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-replication.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-replication.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-replication.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-resource.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-resource.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-resource.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-resource.html 2024-02-05 22:04:10.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 @@ -664,4 +664,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.13/doc/src/sgml/html/runtime-config-short.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-short.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-short.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-short.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-statistics.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-statistics.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-statistics.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-statistics.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config-wal.html postgresql-13-13.14/doc/src/sgml/html/runtime-config-wal.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config-wal.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config-wal.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime-config.html postgresql-13-13.14/doc/src/sgml/html/runtime-config.html --- postgresql-13-13.13/doc/src/sgml/html/runtime-config.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime-config.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/runtime.html postgresql-13-13.14/doc/src/sgml/html/runtime.html --- postgresql-13-13.13/doc/src/sgml/html/runtime.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/runtime.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/sasl-authentication.html postgresql-13-13.14/doc/src/sgml/html/sasl-authentication.html --- postgresql-13-13.13/doc/src/sgml/html/sasl-authentication.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sasl-authentication.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/seg.html postgresql-13-13.14/doc/src/sgml/html/seg.html --- postgresql-13-13.13/doc/src/sgml/html/seg.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/seg.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/sepgsql.html postgresql-13-13.14/doc/src/sgml/html/sepgsql.html --- postgresql-13-13.13/doc/src/sgml/html/sepgsql.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sepgsql.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/server-programming.html postgresql-13-13.14/doc/src/sgml/html/server-programming.html --- postgresql-13-13.13/doc/src/sgml/html/server-programming.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/server-programming.html 2024-02-05 22:04:17.000000000 +0000 @@ -1,5 +1,5 @@ -Part V. Server Programming
    Part V. Server Programming
    Prev UpPostgreSQL 13.13 DocumentationHome Next

    Part V. Server Programming

    +Part V. Server Programming

    Part V. Server Programming
    Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/server-shutdown.html postgresql-13-13.14/doc/src/sgml/html/server-shutdown.html --- postgresql-13-13.13/doc/src/sgml/html/server-shutdown.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/server-shutdown.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/server-start.html postgresql-13-13.14/doc/src/sgml/html/server-start.html --- postgresql-13-13.13/doc/src/sgml/html/server-start.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/server-start.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/source-conventions.html postgresql-13-13.14/doc/src/sgml/html/source-conventions.html --- postgresql-13-13.13/doc/src/sgml/html/source-conventions.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/source-conventions.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/source-format.html postgresql-13-13.14/doc/src/sgml/html/source-format.html --- postgresql-13-13.13/doc/src/sgml/html/source-format.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/source-format.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/source.html postgresql-13-13.14/doc/src/sgml/html/source.html --- postgresql-13-13.13/doc/src/sgml/html/source.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/source.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/sourcerepo.html postgresql-13-13.14/doc/src/sgml/html/sourcerepo.html --- postgresql-13-13.13/doc/src/sgml/html/sourcerepo.html 2023-11-06 22:30:55.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sourcerepo.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/spgist-builtin-opclasses.html postgresql-13-13.14/doc/src/sgml/html/spgist-builtin-opclasses.html --- postgresql-13-13.13/doc/src/sgml/html/spgist-builtin-opclasses.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spgist-builtin-opclasses.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/spgist-examples.html postgresql-13-13.14/doc/src/sgml/html/spgist-examples.html --- postgresql-13-13.13/doc/src/sgml/html/spgist-examples.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spgist-examples.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/spgist-extensibility.html postgresql-13-13.14/doc/src/sgml/html/spgist-extensibility.html --- postgresql-13-13.13/doc/src/sgml/html/spgist-extensibility.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spgist-extensibility.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/spgist-implementation.html postgresql-13-13.14/doc/src/sgml/html/spgist-implementation.html --- postgresql-13-13.13/doc/src/sgml/html/spgist-implementation.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spgist-implementation.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/spgist-intro.html postgresql-13-13.14/doc/src/sgml/html/spgist-intro.html --- postgresql-13-13.13/doc/src/sgml/html/spgist-intro.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spgist-intro.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/spgist.html postgresql-13-13.14/doc/src/sgml/html/spgist.html --- postgresql-13-13.13/doc/src/sgml/html/spgist.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spgist.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/spi-examples.html postgresql-13-13.14/doc/src/sgml/html/spi-examples.html --- postgresql-13-13.13/doc/src/sgml/html/spi-examples.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-examples.html 2024-02-05 22:04:17.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 @@ -167,4 +167,4 @@ 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.13/doc/src/sgml/html/spi-interface-support.html postgresql-13-13.14/doc/src/sgml/html/spi-interface-support.html --- postgresql-13-13.13/doc/src/sgml/html/spi-interface-support.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-interface-support.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-interface.html postgresql-13-13.14/doc/src/sgml/html/spi-interface.html --- postgresql-13-13.13/doc/src/sgml/html/spi-interface.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-interface.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-memory.html postgresql-13-13.14/doc/src/sgml/html/spi-memory.html --- postgresql-13-13.13/doc/src/sgml/html/spi-memory.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-memory.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-realloc.html postgresql-13-13.14/doc/src/sgml/html/spi-realloc.html --- postgresql-13-13.13/doc/src/sgml/html/spi-realloc.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-realloc.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-commit.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-commit.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-commit.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-commit.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-connect.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-connect.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-connect.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-connect.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-copytuple.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-copytuple.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-copytuple.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-copytuple.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-cursor-close.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-close.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-close.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-close.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-cursor-fetch.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-fetch.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-fetch.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-fetch.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-cursor-find.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-find.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-find.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-find.html 2024-02-05 22:04:16.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
@@ -17,4 +17,4 @@
    to other SPI functions, they can defend themselves against such
    cases, but caution is appropriate when directly inspecting
    the Portal.
-  
    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.13/doc/src/sgml/html/spi-spi-cursor-move.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-move.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-move.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-move.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-cursor-open-with-args.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-open-with-args.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-open-with-args.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-open-with-args.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-open-with-paramlist.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-cursor-open.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-open.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-cursor-open.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-cursor-open.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-exec.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-exec.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-exec.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-exec.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-execp.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-execp.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-execp.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-execp.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute-plan-with-paramlist.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-execute-plan.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute-plan.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-execute-plan.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute-plan.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-execute-with-args.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute-with-args.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-execute-with-args.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute-with-args.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-execute.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-execute.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-execute.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-finish.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-finish.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-finish.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-finish.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-fname.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-fname.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-fname.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-fname.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-fnumber.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-fnumber.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-fnumber.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-fnumber.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-freeplan.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-freeplan.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-freeplan.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-freeplan.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-freetuple.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-freetuple.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-freetuple.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-freetuple.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-freetupletable.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-freetupletable.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-freetupletable.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-freetupletable.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-getargcount.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-getargcount.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-getargcount.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-getargcount.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-getargtypeid.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-getargtypeid.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-getargtypeid.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-getargtypeid.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-getbinval.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-getbinval.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-getbinval.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-getbinval.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-getnspname.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-getnspname.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-getnspname.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-getnspname.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-getrelname.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-getrelname.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-getrelname.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-getrelname.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-gettype.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-gettype.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-gettype.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-gettype.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-gettypeid.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-gettypeid.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-gettypeid.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-gettypeid.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-getvalue.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-getvalue.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-getvalue.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-getvalue.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-is-cursor-plan.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-is-cursor-plan.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-is-cursor-plan.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-is-cursor-plan.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-keepplan.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-keepplan.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-keepplan.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-keepplan.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-modifytuple.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-modifytuple.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-modifytuple.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-modifytuple.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-palloc.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-palloc.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-palloc.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-palloc.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-pfree.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-pfree.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-pfree.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-pfree.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-prepare-cursor.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-prepare-cursor.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-prepare-cursor.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-prepare-cursor.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-prepare-params.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-prepare-params.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-prepare-params.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-prepare-params.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-prepare.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-prepare.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-prepare.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-prepare.html 2024-02-05 22:04:16.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.13/doc/src/sgml/html/spi-spi-register-relation.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-register-relation.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-register-relation.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-register-relation.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-register-trigger-data.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-register-trigger-data.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-register-trigger-data.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-register-trigger-data.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-result-code-string.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-result-code-string.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-result-code-string.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-result-code-string.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-returntuple.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-returntuple.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-returntuple.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-returntuple.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-rollback.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-rollback.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-rollback.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-rollback.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-saveplan.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-saveplan.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-saveplan.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-saveplan.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-scroll-cursor-fetch.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-scroll-cursor-move.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-scroll-cursor-move.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-scroll-cursor-move.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-scroll-cursor-move.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-start-transaction.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-start-transaction.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-start-transaction.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-start-transaction.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-spi-unregister-relation.html postgresql-13-13.14/doc/src/sgml/html/spi-spi-unregister-relation.html --- postgresql-13-13.13/doc/src/sgml/html/spi-spi-unregister-relation.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-spi-unregister-relation.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-transaction.html postgresql-13-13.14/doc/src/sgml/html/spi-transaction.html --- postgresql-13-13.13/doc/src/sgml/html/spi-transaction.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-transaction.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi-visibility.html postgresql-13-13.14/doc/src/sgml/html/spi-visibility.html --- postgresql-13-13.13/doc/src/sgml/html/spi-visibility.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi-visibility.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/spi.html postgresql-13-13.14/doc/src/sgml/html/spi.html --- postgresql-13-13.13/doc/src/sgml/html/spi.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/spi.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-abort.html postgresql-13-13.14/doc/src/sgml/html/sql-abort.html --- postgresql-13-13.13/doc/src/sgml/html/sql-abort.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-abort.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-alteraggregate.html postgresql-13-13.14/doc/src/sgml/html/sql-alteraggregate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alteraggregate.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alteraggregate.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-altercollation.html postgresql-13-13.14/doc/src/sgml/html/sql-altercollation.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altercollation.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altercollation.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-alterconversion.html postgresql-13-13.14/doc/src/sgml/html/sql-alterconversion.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterconversion.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterconversion.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-alterdatabase.html postgresql-13-13.14/doc/src/sgml/html/sql-alterdatabase.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterdatabase.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterdatabase.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-alterdefaultprivileges.html postgresql-13-13.14/doc/src/sgml/html/sql-alterdefaultprivileges.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterdefaultprivileges.html 2023-11-06 22:30:38.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterdefaultprivileges.html 2024-02-05 22:04:17.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 [, ...] ]
@@ -160,4 +160,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.13/doc/src/sgml/html/sql-alterdomain.html postgresql-13-13.14/doc/src/sgml/html/sql-alterdomain.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterdomain.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterdomain.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-altereventtrigger.html postgresql-13-13.14/doc/src/sgml/html/sql-altereventtrigger.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altereventtrigger.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altereventtrigger.html 2024-02-05 22:04:17.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 }
@@ -15,11 +15,11 @@
       The user name of the new owner of the event trigger.
    new_name

    The new name of the event trigger. -

    DISABLE/ENABLE [ REPLICA | ALWAYS ] TRIGGER

    +

    DISABLE/ENABLE [ REPLICA | ALWAYS ]

    These forms configure the firing of event triggers. A disabled trigger is still known to the system, but is not executed when its triggering event occurs. See also session_replication_role.

    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.13/doc/src/sgml/html/sql-alterextension.html postgresql-13-13.14/doc/src/sgml/html/sql-alterextension.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterextension.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterextension.html 2024-02-05 22:04:17.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.13/doc/src/sgml/html/sql-alterforeigndatawrapper.html postgresql-13-13.14/doc/src/sgml/html/sql-alterforeigndatawrapper.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterforeigndatawrapper.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterforeigndatawrapper.html 2024-02-05 22:04:17.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 ]
@@ -53,7 +53,7 @@
    Change a foreign-data wrapper dbi, add
    option foo, drop bar:
 
    -ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP 'bar');
+ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP bar);
 
    
   
    
    Change the foreign-data wrapper dbi 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.13/doc/src/sgml/html/sql-alterforeigntable.html postgresql-13-13.14/doc/src/sgml/html/sql-alterforeigntable.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterforeigntable.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterforeigntable.html 2024-02-05 22:04:18.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 [ * ]
@@ -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.13/doc/src/sgml/html/sql-alterfunction.html postgresql-13-13.14/doc/src/sgml/html/sql-alterfunction.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterfunction.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterfunction.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altergroup.html postgresql-13-13.14/doc/src/sgml/html/sql-altergroup.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altergroup.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altergroup.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterindex.html postgresql-13-13.14/doc/src/sgml/html/sql-alterindex.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterindex.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterindex.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterlanguage.html postgresql-13-13.14/doc/src/sgml/html/sql-alterlanguage.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterlanguage.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterlanguage.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterlargeobject.html postgresql-13-13.14/doc/src/sgml/html/sql-alterlargeobject.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterlargeobject.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterlargeobject.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altermaterializedview.html postgresql-13-13.14/doc/src/sgml/html/sql-altermaterializedview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altermaterializedview.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altermaterializedview.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alteropclass.html postgresql-13-13.14/doc/src/sgml/html/sql-alteropclass.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alteropclass.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alteropclass.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alteroperator.html postgresql-13-13.14/doc/src/sgml/html/sql-alteroperator.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alteroperator.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alteroperator.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alteropfamily.html postgresql-13-13.14/doc/src/sgml/html/sql-alteropfamily.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alteropfamily.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alteropfamily.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterpolicy.html postgresql-13-13.14/doc/src/sgml/html/sql-alterpolicy.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterpolicy.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterpolicy.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterprocedure.html postgresql-13-13.14/doc/src/sgml/html/sql-alterprocedure.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterprocedure.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterprocedure.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterpublication.html postgresql-13-13.14/doc/src/sgml/html/sql-alterpublication.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterpublication.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterpublication.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterrole.html postgresql-13-13.14/doc/src/sgml/html/sql-alterrole.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterrole.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterrole.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterroutine.html postgresql-13-13.14/doc/src/sgml/html/sql-alterroutine.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterroutine.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterroutine.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterrule.html postgresql-13-13.14/doc/src/sgml/html/sql-alterrule.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterrule.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterrule.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterschema.html postgresql-13-13.14/doc/src/sgml/html/sql-alterschema.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterschema.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterschema.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altersequence.html postgresql-13-13.14/doc/src/sgml/html/sql-altersequence.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altersequence.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altersequence.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterserver.html postgresql-13-13.14/doc/src/sgml/html/sql-alterserver.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterserver.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterserver.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterstatistics.html postgresql-13-13.14/doc/src/sgml/html/sql-alterstatistics.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterstatistics.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterstatistics.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altersubscription.html postgresql-13-13.14/doc/src/sgml/html/sql-altersubscription.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altersubscription.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altersubscription.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altersystem.html postgresql-13-13.14/doc/src/sgml/html/sql-altersystem.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altersystem.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altersystem.html 2024-02-05 22:04:18.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 [, ...] | DEFAULT }
 
 ALTER SYSTEM RESET configuration_parameter
@@ -61,4 +61,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.13/doc/src/sgml/html/sql-altertable.html postgresql-13-13.14/doc/src/sgml/html/sql-altertable.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertable.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertable.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertablespace.html postgresql-13-13.14/doc/src/sgml/html/sql-altertablespace.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertablespace.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertablespace.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertrigger.html postgresql-13-13.14/doc/src/sgml/html/sql-altertrigger.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertrigger.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertrigger.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertsconfig.html postgresql-13-13.14/doc/src/sgml/html/sql-altertsconfig.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertsconfig.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertsconfig.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertsdictionary.html postgresql-13-13.14/doc/src/sgml/html/sql-altertsdictionary.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertsdictionary.html 2023-11-06 22:30:39.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertsdictionary.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertsparser.html postgresql-13-13.14/doc/src/sgml/html/sql-altertsparser.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertsparser.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertsparser.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertstemplate.html postgresql-13-13.14/doc/src/sgml/html/sql-altertstemplate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertstemplate.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertstemplate.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-altertype.html postgresql-13-13.14/doc/src/sgml/html/sql-altertype.html --- postgresql-13-13.13/doc/src/sgml/html/sql-altertype.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-altertype.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alteruser.html postgresql-13-13.14/doc/src/sgml/html/sql-alteruser.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alteruser.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alteruser.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterusermapping.html postgresql-13-13.14/doc/src/sgml/html/sql-alterusermapping.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterusermapping.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterusermapping.html 2024-02-05 22:04:18.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.13/doc/src/sgml/html/sql-alterview.html postgresql-13-13.14/doc/src/sgml/html/sql-alterview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-alterview.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-alterview.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-analyze.html postgresql-13-13.14/doc/src/sgml/html/sql-analyze.html --- postgresql-13-13.13/doc/src/sgml/html/sql-analyze.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-analyze.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-begin.html postgresql-13-13.14/doc/src/sgml/html/sql-begin.html --- postgresql-13-13.13/doc/src/sgml/html/sql-begin.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-begin.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-call.html postgresql-13-13.14/doc/src/sgml/html/sql-call.html --- postgresql-13-13.13/doc/src/sgml/html/sql-call.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-call.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-checkpoint.html postgresql-13-13.14/doc/src/sgml/html/sql-checkpoint.html --- postgresql-13-13.13/doc/src/sgml/html/sql-checkpoint.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-checkpoint.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-close.html postgresql-13-13.14/doc/src/sgml/html/sql-close.html --- postgresql-13-13.13/doc/src/sgml/html/sql-close.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-close.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-cluster.html postgresql-13-13.14/doc/src/sgml/html/sql-cluster.html --- postgresql-13-13.13/doc/src/sgml/html/sql-cluster.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-cluster.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-commands.html postgresql-13-13.14/doc/src/sgml/html/sql-commands.html --- postgresql-13-13.13/doc/src/sgml/html/sql-commands.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-commands.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-comment.html postgresql-13-13.14/doc/src/sgml/html/sql-comment.html --- postgresql-13-13.13/doc/src/sgml/html/sql-comment.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-comment.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-commit-prepared.html postgresql-13-13.14/doc/src/sgml/html/sql-commit-prepared.html --- postgresql-13-13.13/doc/src/sgml/html/sql-commit-prepared.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-commit-prepared.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-commit.html postgresql-13-13.14/doc/src/sgml/html/sql-commit.html --- postgresql-13-13.13/doc/src/sgml/html/sql-commit.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-commit.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-copy.html postgresql-13-13.14/doc/src/sgml/html/sql-copy.html --- postgresql-13-13.13/doc/src/sgml/html/sql-copy.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-copy.html 2024-02-05 22:04:19.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 [, ...] ) ]
@@ -63,10 +63,10 @@
       copied.  Note that parentheses are required around the query.
      
    
       For INSERT, UPDATE and
-      DELETE queries a RETURNING clause must be provided,
-      and the target relation must not have a conditional rule, nor
-      an ALSO rule, nor an INSTEAD rule
-      that expands to multiple statements.
+      DELETE queries a RETURNING clause
+      must be provided, and the target relation must not have a conditional
+      rule, nor an ALSO rule, nor an
+      INSTEAD rule that expands to multiple statements.
      
    filename
    
       The path name of the input or output file.  An input file name can be
       an absolute or relative path, but an output file name must be an absolute
@@ -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.13/doc/src/sgml/html/sql-create-access-method.html postgresql-13-13.14/doc/src/sgml/html/sql-create-access-method.html --- postgresql-13-13.13/doc/src/sgml/html/sql-create-access-method.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-create-access-method.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createaggregate.html postgresql-13-13.14/doc/src/sgml/html/sql-createaggregate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createaggregate.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createaggregate.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createcast.html postgresql-13-13.14/doc/src/sgml/html/sql-createcast.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createcast.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createcast.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createcollation.html postgresql-13-13.14/doc/src/sgml/html/sql-createcollation.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createcollation.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createcollation.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createconversion.html postgresql-13-13.14/doc/src/sgml/html/sql-createconversion.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createconversion.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createconversion.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createdatabase.html postgresql-13-13.14/doc/src/sgml/html/sql-createdatabase.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createdatabase.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createdatabase.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createdomain.html postgresql-13-13.14/doc/src/sgml/html/sql-createdomain.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createdomain.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createdomain.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createeventtrigger.html postgresql-13-13.14/doc/src/sgml/html/sql-createeventtrigger.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createeventtrigger.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createeventtrigger.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createextension.html postgresql-13-13.14/doc/src/sgml/html/sql-createextension.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createextension.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createextension.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createforeigndatawrapper.html postgresql-13-13.14/doc/src/sgml/html/sql-createforeigndatawrapper.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createforeigndatawrapper.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createforeigndatawrapper.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createforeigntable.html postgresql-13-13.14/doc/src/sgml/html/sql-createforeigntable.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createforeigntable.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createforeigntable.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createfunction.html postgresql-13-13.14/doc/src/sgml/html/sql-createfunction.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createfunction.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createfunction.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-creategroup.html postgresql-13-13.14/doc/src/sgml/html/sql-creategroup.html --- postgresql-13-13.13/doc/src/sgml/html/sql-creategroup.html 2023-11-06 22:30:40.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-creategroup.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createindex.html postgresql-13-13.14/doc/src/sgml/html/sql-createindex.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createindex.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createindex.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createlanguage.html postgresql-13-13.14/doc/src/sgml/html/sql-createlanguage.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createlanguage.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createlanguage.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-creatematerializedview.html postgresql-13-13.14/doc/src/sgml/html/sql-creatematerializedview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-creatematerializedview.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-creatematerializedview.html 2024-02-05 22:04:19.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.13/doc/src/sgml/html/sql-createopclass.html postgresql-13-13.14/doc/src/sgml/html/sql-createopclass.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createopclass.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createopclass.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createoperator.html postgresql-13-13.14/doc/src/sgml/html/sql-createoperator.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createoperator.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createoperator.html 2024-02-05 22:04:19.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 ]
@@ -139,4 +139,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.13/doc/src/sgml/html/sql-createopfamily.html postgresql-13-13.14/doc/src/sgml/html/sql-createopfamily.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createopfamily.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createopfamily.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createpolicy.html postgresql-13-13.14/doc/src/sgml/html/sql-createpolicy.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createpolicy.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createpolicy.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createprocedure.html postgresql-13-13.14/doc/src/sgml/html/sql-createprocedure.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createprocedure.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createprocedure.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createpublication.html postgresql-13-13.14/doc/src/sgml/html/sql-createpublication.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createpublication.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createpublication.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createrole.html postgresql-13-13.14/doc/src/sgml/html/sql-createrole.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createrole.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createrole.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createrule.html postgresql-13-13.14/doc/src/sgml/html/sql-createrule.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createrule.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createrule.html 2024-02-05 22:04:20.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 ... ) }
@@ -173,4 +173,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.13/doc/src/sgml/html/sql-createschema.html postgresql-13-13.14/doc/src/sgml/html/sql-createschema.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createschema.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createschema.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createsequence.html postgresql-13-13.14/doc/src/sgml/html/sql-createsequence.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createsequence.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createsequence.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createserver.html postgresql-13-13.14/doc/src/sgml/html/sql-createserver.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createserver.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createserver.html 2024-02-05 22:04:20.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' [, ... ] ) ]
@@ -53,4 +53,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.13/doc/src/sgml/html/sql-createstatistics.html postgresql-13-13.14/doc/src/sgml/html/sql-createstatistics.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createstatistics.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createstatistics.html 2024-02-05 22:04:20.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 [, ...]
@@ -114,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.13/doc/src/sgml/html/sql-createsubscription.html postgresql-13-13.14/doc/src/sgml/html/sql-createsubscription.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createsubscription.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createsubscription.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtable.html postgresql-13-13.14/doc/src/sgml/html/sql-createtable.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtable.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtable.html 2024-02-05 22:04:20.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
@@ -665,10 +665,11 @@
       contain values that match values in the referenced
       column(s) of some row of the referenced table.  If the refcolumn list is omitted, the
       primary key of the reftable
-      is used.  The referenced columns must be the columns of a non-deferrable
-      unique or primary key constraint in the referenced table.  The user
-      must have REFERENCES permission on the referenced table
-      (either the whole table, or the specific referenced columns).  The
+      is used.  Otherwise, the refcolumn
+      list must refer to the columns of a non-deferrable unique or primary key
+      constraint or be the columns of a non-partial unique index.  The user
+      must have REFERENCES permission on the referenced
+      table (either the whole table, or the specific referenced columns).  The
       addition of a foreign key constraint requires a
       SHARE ROW EXCLUSIVE lock on the referenced table.
       Note that foreign key constraints cannot be defined between temporary
@@ -1339,14 +1340,18 @@
    
    EXCLUDE Constraint
    
     The EXCLUDE constraint type is a
     PostgreSQL extension.
-   
    NULL “Constraint”
    
+   
    Foreign Key Constraints
    
+    It is a PostgreSQL extension that a
+    foreign key constraint may reference columns of a unique index instead of
+    columns of a primary key or unique constraint.
+   
    NULL “Constraint”
    
     The NULL “constraint” (actually a
     non-constraint) is a PostgreSQL
     extension to the SQL standard that is included for compatibility with some
     other database systems (and for symmetry with the NOT
     NULL constraint).  Since it is the default for any
     column, its presence is simply noise.
-   
    Constraint Naming
    
+   
    Constraint Naming
    
     The SQL standard says that table and domain constraints must have names
     that are unique across the schema containing the table or domain.
     PostgreSQL is laxer: it only requires
@@ -1362,21 +1367,21 @@
     for NOT NULL constraints at all, so they are not
     subject to the uniqueness restriction.  This might change in a future
     release.
-   
    Inheritance
    
+   
    Inheritance
    
     Multiple inheritance via the INHERITS clause is
     a PostgreSQL language extension.
     SQL:1999 and later define single inheritance using a
     different syntax and different semantics.  SQL:1999-style
     inheritance is not yet supported by
     PostgreSQL.
-   
    Zero-Column Tables
    
+   
    Zero-Column Tables
    
     PostgreSQL allows a table of no columns
     to be created (for example, CREATE TABLE foo();).  This
     is an extension from the SQL standard, which does not allow zero-column
     tables.  Zero-column tables are not in themselves very useful, but
     disallowing them creates odd special cases for ALTER TABLE
     DROP COLUMN, so it seems cleaner to ignore this spec restriction.
-   
    Multiple Identity Columns
    
+   
    Multiple Identity Columns
    
     PostgreSQL allows a table to have more than one
     identity column.  The standard specifies that a table can have at most one
     identity column.  This is relaxed mainly to give more flexibility for
@@ -1384,33 +1389,33 @@
     the INSERT command supports only one override clause
     that applies to the entire statement, so having multiple identity columns
     with different behaviors is not well supported.
-   
    Generated Columns
    
+   
    Generated Columns
    
     The option STORED is not standard but is also used by
     other SQL implementations.  The SQL standard does not specify the storage
     of generated columns.
-   
    LIKE Clause
    
+   
    LIKE Clause
    
     While a LIKE clause exists in the SQL standard, many of the
     options that PostgreSQL accepts for it are not
     in the standard, and some of the standard's options are not implemented
     by PostgreSQL.
-   
    WITH Clause
    
+   
    WITH Clause
    
     The WITH clause is a PostgreSQL
     extension; storage parameters are not in the standard.
-   
    Tablespaces
    
+   
    Tablespaces
    
     The PostgreSQL concept of tablespaces is not
     part of the standard.  Hence, the clauses TABLESPACE
     and USING INDEX TABLESPACE are extensions.
-   
    Typed Tables
    
+   
    Typed Tables
    
     Typed tables implement a subset of the SQL standard.  According to
     the standard, a typed table has columns corresponding to the
     underlying composite type as well as one other column that is
     the “self-referencing column”.
     PostgreSQL does not support self-referencing
     columns explicitly.
-   
    PARTITION BY Clause
    
+   
    PARTITION BY Clause
    
     The PARTITION BY clause is a
     PostgreSQL extension.
-   
    PARTITION OF Clause
    
+   
    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.13/doc/src/sgml/html/sql-createtableas.html postgresql-13-13.14/doc/src/sgml/html/sql-createtableas.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtableas.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtableas.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtablespace.html postgresql-13-13.14/doc/src/sgml/html/sql-createtablespace.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtablespace.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtablespace.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtransform.html postgresql-13-13.14/doc/src/sgml/html/sql-createtransform.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtransform.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtransform.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtrigger.html postgresql-13-13.14/doc/src/sgml/html/sql-createtrigger.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtrigger.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtrigger.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtsconfig.html postgresql-13-13.14/doc/src/sgml/html/sql-createtsconfig.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtsconfig.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtsconfig.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtsdictionary.html postgresql-13-13.14/doc/src/sgml/html/sql-createtsdictionary.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtsdictionary.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtsdictionary.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtsparser.html postgresql-13-13.14/doc/src/sgml/html/sql-createtsparser.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtsparser.html 2023-11-06 22:30:41.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtsparser.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtstemplate.html postgresql-13-13.14/doc/src/sgml/html/sql-createtstemplate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtstemplate.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtstemplate.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createtype.html postgresql-13-13.14/doc/src/sgml/html/sql-createtype.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createtype.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createtype.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createuser.html postgresql-13-13.14/doc/src/sgml/html/sql-createuser.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createuser.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createuser.html 2024-02-05 22:04:20.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.13/doc/src/sgml/html/sql-createusermapping.html postgresql-13-13.14/doc/src/sgml/html/sql-createusermapping.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createusermapping.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createusermapping.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-createview.html postgresql-13-13.14/doc/src/sgml/html/sql-createview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-createview.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-createview.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-deallocate.html postgresql-13-13.14/doc/src/sgml/html/sql-deallocate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-deallocate.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-deallocate.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-declare.html postgresql-13-13.14/doc/src/sgml/html/sql-declare.html --- postgresql-13-13.13/doc/src/sgml/html/sql-declare.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-declare.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-delete.html postgresql-13-13.14/doc/src/sgml/html/sql-delete.html --- postgresql-13-13.13/doc/src/sgml/html/sql-delete.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-delete.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-discard.html postgresql-13-13.14/doc/src/sgml/html/sql-discard.html --- postgresql-13-13.13/doc/src/sgml/html/sql-discard.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-discard.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-do.html postgresql-13-13.14/doc/src/sgml/html/sql-do.html --- postgresql-13-13.13/doc/src/sgml/html/sql-do.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-do.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-drop-access-method.html postgresql-13-13.14/doc/src/sgml/html/sql-drop-access-method.html --- postgresql-13-13.13/doc/src/sgml/html/sql-drop-access-method.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-drop-access-method.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-drop-owned.html postgresql-13-13.14/doc/src/sgml/html/sql-drop-owned.html --- postgresql-13-13.13/doc/src/sgml/html/sql-drop-owned.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-drop-owned.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropaggregate.html postgresql-13-13.14/doc/src/sgml/html/sql-dropaggregate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropaggregate.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropaggregate.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropcast.html postgresql-13-13.14/doc/src/sgml/html/sql-dropcast.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropcast.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropcast.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropcollation.html postgresql-13-13.14/doc/src/sgml/html/sql-dropcollation.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropcollation.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropcollation.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropconversion.html postgresql-13-13.14/doc/src/sgml/html/sql-dropconversion.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropconversion.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropconversion.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropdatabase.html postgresql-13-13.14/doc/src/sgml/html/sql-dropdatabase.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropdatabase.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropdatabase.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropdomain.html postgresql-13-13.14/doc/src/sgml/html/sql-dropdomain.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropdomain.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropdomain.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropeventtrigger.html postgresql-13-13.14/doc/src/sgml/html/sql-dropeventtrigger.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropeventtrigger.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropeventtrigger.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropextension.html postgresql-13-13.14/doc/src/sgml/html/sql-dropextension.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropextension.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropextension.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropforeigndatawrapper.html postgresql-13-13.14/doc/src/sgml/html/sql-dropforeigndatawrapper.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropforeigndatawrapper.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropforeigndatawrapper.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropforeigntable.html postgresql-13-13.14/doc/src/sgml/html/sql-dropforeigntable.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropforeigntable.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropforeigntable.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropfunction.html postgresql-13-13.14/doc/src/sgml/html/sql-dropfunction.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropfunction.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropfunction.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropgroup.html postgresql-13-13.14/doc/src/sgml/html/sql-dropgroup.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropgroup.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropgroup.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropindex.html postgresql-13-13.14/doc/src/sgml/html/sql-dropindex.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropindex.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropindex.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-droplanguage.html postgresql-13-13.14/doc/src/sgml/html/sql-droplanguage.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droplanguage.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droplanguage.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropmaterializedview.html postgresql-13-13.14/doc/src/sgml/html/sql-dropmaterializedview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropmaterializedview.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropmaterializedview.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropopclass.html postgresql-13-13.14/doc/src/sgml/html/sql-dropopclass.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropopclass.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropopclass.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropoperator.html postgresql-13-13.14/doc/src/sgml/html/sql-dropoperator.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropoperator.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropoperator.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropopfamily.html postgresql-13-13.14/doc/src/sgml/html/sql-dropopfamily.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropopfamily.html 2023-11-06 22:30:42.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropopfamily.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-droppolicy.html postgresql-13-13.14/doc/src/sgml/html/sql-droppolicy.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droppolicy.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droppolicy.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropprocedure.html postgresql-13-13.14/doc/src/sgml/html/sql-dropprocedure.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropprocedure.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropprocedure.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-droppublication.html postgresql-13-13.14/doc/src/sgml/html/sql-droppublication.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droppublication.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droppublication.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-droprole.html postgresql-13-13.14/doc/src/sgml/html/sql-droprole.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droprole.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droprole.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-droproutine.html postgresql-13-13.14/doc/src/sgml/html/sql-droproutine.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droproutine.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droproutine.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-droprule.html postgresql-13-13.14/doc/src/sgml/html/sql-droprule.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droprule.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droprule.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropschema.html postgresql-13-13.14/doc/src/sgml/html/sql-dropschema.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropschema.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropschema.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropsequence.html postgresql-13-13.14/doc/src/sgml/html/sql-dropsequence.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropsequence.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropsequence.html 2024-02-05 22:04:21.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.13/doc/src/sgml/html/sql-dropserver.html postgresql-13-13.14/doc/src/sgml/html/sql-dropserver.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropserver.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropserver.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-dropstatistics.html postgresql-13-13.14/doc/src/sgml/html/sql-dropstatistics.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropstatistics.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropstatistics.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-dropsubscription.html postgresql-13-13.14/doc/src/sgml/html/sql-dropsubscription.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropsubscription.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropsubscription.html 2024-02-05 22:04:22.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
@@ -44,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.13/doc/src/sgml/html/sql-droptable.html postgresql-13-13.14/doc/src/sgml/html/sql-droptable.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptable.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptable.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptablespace.html postgresql-13-13.14/doc/src/sgml/html/sql-droptablespace.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptablespace.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptablespace.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptransform.html postgresql-13-13.14/doc/src/sgml/html/sql-droptransform.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptransform.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptransform.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptrigger.html postgresql-13-13.14/doc/src/sgml/html/sql-droptrigger.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptrigger.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptrigger.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptsconfig.html postgresql-13-13.14/doc/src/sgml/html/sql-droptsconfig.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptsconfig.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptsconfig.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptsdictionary.html postgresql-13-13.14/doc/src/sgml/html/sql-droptsdictionary.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptsdictionary.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptsdictionary.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptsparser.html postgresql-13-13.14/doc/src/sgml/html/sql-droptsparser.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptsparser.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptsparser.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptstemplate.html postgresql-13-13.14/doc/src/sgml/html/sql-droptstemplate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptstemplate.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptstemplate.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-droptype.html postgresql-13-13.14/doc/src/sgml/html/sql-droptype.html --- postgresql-13-13.13/doc/src/sgml/html/sql-droptype.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-droptype.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-dropuser.html postgresql-13-13.14/doc/src/sgml/html/sql-dropuser.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropuser.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropuser.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-dropusermapping.html postgresql-13-13.14/doc/src/sgml/html/sql-dropusermapping.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropusermapping.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropusermapping.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-dropview.html postgresql-13-13.14/doc/src/sgml/html/sql-dropview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-dropview.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-dropview.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-end.html postgresql-13-13.14/doc/src/sgml/html/sql-end.html --- postgresql-13-13.13/doc/src/sgml/html/sql-end.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-end.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-execute.html postgresql-13-13.14/doc/src/sgml/html/sql-execute.html --- postgresql-13-13.13/doc/src/sgml/html/sql-execute.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-execute.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-explain.html postgresql-13-13.14/doc/src/sgml/html/sql-explain.html --- postgresql-13-13.13/doc/src/sgml/html/sql-explain.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-explain.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-expressions.html postgresql-13-13.14/doc/src/sgml/html/sql-expressions.html --- postgresql-13-13.13/doc/src/sgml/html/sql-expressions.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-expressions.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/sql-fetch.html postgresql-13-13.14/doc/src/sgml/html/sql-fetch.html --- postgresql-13-13.13/doc/src/sgml/html/sql-fetch.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-fetch.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-grant.html postgresql-13-13.14/doc/src/sgml/html/sql-grant.html --- postgresql-13-13.13/doc/src/sgml/html/sql-grant.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-grant.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-importforeignschema.html postgresql-13-13.14/doc/src/sgml/html/sql-importforeignschema.html --- postgresql-13-13.13/doc/src/sgml/html/sql-importforeignschema.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-importforeignschema.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-insert.html postgresql-13-13.14/doc/src/sgml/html/sql-insert.html --- postgresql-13-13.13/doc/src/sgml/html/sql-insert.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-insert.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-keywords-appendix.html postgresql-13-13.14/doc/src/sgml/html/sql-keywords-appendix.html --- postgresql-13-13.13/doc/src/sgml/html/sql-keywords-appendix.html 2023-11-06 22:30:52.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-keywords-appendix.html 2024-02-05 22:04:30.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.13. Background information can be found in Section 4.1.1. + 13.14. 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.13/doc/src/sgml/html/sql-listen.html postgresql-13-13.14/doc/src/sgml/html/sql-listen.html --- postgresql-13-13.13/doc/src/sgml/html/sql-listen.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-listen.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-load.html postgresql-13-13.14/doc/src/sgml/html/sql-load.html --- postgresql-13-13.13/doc/src/sgml/html/sql-load.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-load.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-lock.html postgresql-13-13.14/doc/src/sgml/html/sql-lock.html --- postgresql-13-13.13/doc/src/sgml/html/sql-lock.html 2023-11-06 22:30:43.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-lock.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-move.html postgresql-13-13.14/doc/src/sgml/html/sql-move.html --- postgresql-13-13.13/doc/src/sgml/html/sql-move.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-move.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-notify.html postgresql-13-13.14/doc/src/sgml/html/sql-notify.html --- postgresql-13-13.13/doc/src/sgml/html/sql-notify.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-notify.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-prepare-transaction.html postgresql-13-13.14/doc/src/sgml/html/sql-prepare-transaction.html --- postgresql-13-13.13/doc/src/sgml/html/sql-prepare-transaction.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-prepare-transaction.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-prepare.html postgresql-13-13.14/doc/src/sgml/html/sql-prepare.html --- postgresql-13-13.13/doc/src/sgml/html/sql-prepare.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-prepare.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-reassign-owned.html postgresql-13-13.14/doc/src/sgml/html/sql-reassign-owned.html --- postgresql-13-13.13/doc/src/sgml/html/sql-reassign-owned.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-reassign-owned.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-refreshmaterializedview.html postgresql-13-13.14/doc/src/sgml/html/sql-refreshmaterializedview.html --- postgresql-13-13.13/doc/src/sgml/html/sql-refreshmaterializedview.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-refreshmaterializedview.html 2024-02-05 22:04:22.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.13/doc/src/sgml/html/sql-reindex.html postgresql-13-13.14/doc/src/sgml/html/sql-reindex.html --- postgresql-13-13.13/doc/src/sgml/html/sql-reindex.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-reindex.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-release-savepoint.html postgresql-13-13.14/doc/src/sgml/html/sql-release-savepoint.html --- postgresql-13-13.13/doc/src/sgml/html/sql-release-savepoint.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-release-savepoint.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-reset.html postgresql-13-13.14/doc/src/sgml/html/sql-reset.html --- postgresql-13-13.13/doc/src/sgml/html/sql-reset.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-reset.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-revoke.html postgresql-13-13.14/doc/src/sgml/html/sql-revoke.html --- postgresql-13-13.13/doc/src/sgml/html/sql-revoke.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-revoke.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-rollback-prepared.html postgresql-13-13.14/doc/src/sgml/html/sql-rollback-prepared.html --- postgresql-13-13.13/doc/src/sgml/html/sql-rollback-prepared.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-rollback-prepared.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-rollback-to.html postgresql-13-13.14/doc/src/sgml/html/sql-rollback-to.html --- postgresql-13-13.13/doc/src/sgml/html/sql-rollback-to.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-rollback-to.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-rollback.html postgresql-13-13.14/doc/src/sgml/html/sql-rollback.html --- postgresql-13-13.13/doc/src/sgml/html/sql-rollback.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-rollback.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-savepoint.html postgresql-13-13.14/doc/src/sgml/html/sql-savepoint.html --- postgresql-13-13.13/doc/src/sgml/html/sql-savepoint.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-savepoint.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-security-label.html postgresql-13-13.14/doc/src/sgml/html/sql-security-label.html --- postgresql-13-13.13/doc/src/sgml/html/sql-security-label.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-security-label.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-select.html postgresql-13-13.14/doc/src/sgml/html/sql-select.html --- postgresql-13-13.13/doc/src/sgml/html/sql-select.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-select.html 2024-02-05 22:04:23.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 ] [, ...] ]
@@ -1370,8 +1370,7 @@
   )
 SELECT * FROM t
 UNION ALL
-SELECT * FROM t
-
+SELECT * FROM t;
          x          
 --------------------
   0.534150459803641
@@ -1562,4 +1561,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.13/doc/src/sgml/html/sql-selectinto.html postgresql-13-13.14/doc/src/sgml/html/sql-selectinto.html --- postgresql-13-13.13/doc/src/sgml/html/sql-selectinto.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-selectinto.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-set-constraints.html postgresql-13-13.14/doc/src/sgml/html/sql-set-constraints.html --- postgresql-13-13.13/doc/src/sgml/html/sql-set-constraints.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-set-constraints.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-set-role.html postgresql-13-13.14/doc/src/sgml/html/sql-set-role.html --- postgresql-13-13.13/doc/src/sgml/html/sql-set-role.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-set-role.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-set-session-authorization.html postgresql-13-13.14/doc/src/sgml/html/sql-set-session-authorization.html --- postgresql-13-13.13/doc/src/sgml/html/sql-set-session-authorization.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-set-session-authorization.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-set-transaction.html postgresql-13-13.14/doc/src/sgml/html/sql-set-transaction.html --- postgresql-13-13.13/doc/src/sgml/html/sql-set-transaction.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-set-transaction.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-set.html postgresql-13-13.14/doc/src/sgml/html/sql-set.html --- postgresql-13-13.13/doc/src/sgml/html/sql-set.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-set.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-show.html postgresql-13-13.14/doc/src/sgml/html/sql-show.html --- postgresql-13-13.13/doc/src/sgml/html/sql-show.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-show.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-start-transaction.html postgresql-13-13.14/doc/src/sgml/html/sql-start-transaction.html --- postgresql-13-13.13/doc/src/sgml/html/sql-start-transaction.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-start-transaction.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-syntax-calling-funcs.html postgresql-13-13.14/doc/src/sgml/html/sql-syntax-calling-funcs.html --- postgresql-13-13.13/doc/src/sgml/html/sql-syntax-calling-funcs.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-syntax-calling-funcs.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/sql-syntax-lexical.html postgresql-13-13.14/doc/src/sgml/html/sql-syntax-lexical.html --- postgresql-13-13.13/doc/src/sgml/html/sql-syntax-lexical.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-syntax-lexical.html 2024-02-05 22:04:04.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 @@ -611,7 +611,7 @@ into the parser. Add parentheses if you want an expression with multiple operators to be parsed in some other way than what the precedence rules imply. -

    Table 4.2. Operator Precedence (highest to lowest)

    Operator/ElementAssociativityDescription
    .lefttable/column name separator
    ::leftPostgreSQL-style typecast
    [ ]leftarray element selection
    + -rightunary plus, unary minus
    ^leftexponentiation
    * / %leftmultiplication, division, modulo
    + -leftaddition, subtraction
    (any other operator)leftall other native and user-defined operators
    BETWEEN IN LIKE ILIKE SIMILAR range containment, set membership, string matching
    < > = <= >= <> +

    Table 4.2. Operator Precedence (highest to lowest)

    Operator/ElementAssociativityDescription
    .lefttable/column name separator
    ::leftPostgreSQL-style typecast
    [ ]leftarray element selection
    + -rightunary plus, unary minus
    COLLATEleftcollation selection
    ATleftAT TIME ZONE
    ^leftexponentiation
    * / %leftmultiplication, division, modulo
    + -leftaddition, subtraction
    (any other operator)leftall other native and user-defined operators
    BETWEEN IN LIKE ILIKE SIMILAR range containment, set membership, string matching
    < > = <= >= <>  comparison operators
    IS ISNULL NOTNULL IS TRUE, IS FALSE, IS NULL, IS DISTINCT FROM, etc
    NOTrightlogical negation
    ANDleftlogical conjunction
    ORleftlogical disjunction

    Note that the operator precedence rules also apply to user-defined @@ -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.13/doc/src/sgml/html/sql-syntax.html postgresql-13-13.14/doc/src/sgml/html/sql-syntax.html --- postgresql-13-13.13/doc/src/sgml/html/sql-syntax.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-syntax.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/sql-truncate.html postgresql-13-13.14/doc/src/sgml/html/sql-truncate.html --- postgresql-13-13.13/doc/src/sgml/html/sql-truncate.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-truncate.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-unlisten.html postgresql-13-13.14/doc/src/sgml/html/sql-unlisten.html --- postgresql-13-13.13/doc/src/sgml/html/sql-unlisten.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-unlisten.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-update.html postgresql-13-13.14/doc/src/sgml/html/sql-update.html --- postgresql-13-13.13/doc/src/sgml/html/sql-update.html 2023-11-06 22:30:44.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-update.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-vacuum.html postgresql-13-13.14/doc/src/sgml/html/sql-vacuum.html --- postgresql-13-13.13/doc/src/sgml/html/sql-vacuum.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-vacuum.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql-values.html postgresql-13-13.14/doc/src/sgml/html/sql-values.html --- postgresql-13-13.13/doc/src/sgml/html/sql-values.html 2023-11-06 22:30:45.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql-values.html 2024-02-05 22:04:23.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.13/doc/src/sgml/html/sql.html postgresql-13-13.14/doc/src/sgml/html/sql.html --- postgresql-13-13.13/doc/src/sgml/html/sql.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sql.html 2024-02-05 22:04:09.000000000 +0000 @@ -1,5 +1,5 @@ -Part II. The SQL Language
    Part II. The SQL Language
    Prev UpPostgreSQL 13.13 DocumentationHome Next

    Part II. The SQL Language

    +Part II. The SQL Language

    Part II. The SQL Language
    Prev UpPostgreSQL 13.14 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.13/doc/src/sgml/html/ssh-tunnels.html postgresql-13-13.14/doc/src/sgml/html/ssh-tunnels.html --- postgresql-13-13.13/doc/src/sgml/html/ssh-tunnels.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ssh-tunnels.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/ssl-tcp.html postgresql-13-13.14/doc/src/sgml/html/ssl-tcp.html --- postgresql-13-13.13/doc/src/sgml/html/ssl-tcp.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/ssl-tcp.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/sslinfo.html postgresql-13-13.14/doc/src/sgml/html/sslinfo.html --- postgresql-13-13.13/doc/src/sgml/html/sslinfo.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sslinfo.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/sspi-auth.html postgresql-13-13.14/doc/src/sgml/html/sspi-auth.html --- postgresql-13-13.13/doc/src/sgml/html/sspi-auth.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/sspi-auth.html 2024-02-05 22:04:10.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 @@ -67,4 +67,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.13/doc/src/sgml/html/storage-file-layout.html postgresql-13-13.14/doc/src/sgml/html/storage-file-layout.html --- postgresql-13-13.13/doc/src/sgml/html/storage-file-layout.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-file-layout.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/storage-fsm.html postgresql-13-13.14/doc/src/sgml/html/storage-fsm.html --- postgresql-13-13.13/doc/src/sgml/html/storage-fsm.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-fsm.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/storage-hot.html postgresql-13-13.14/doc/src/sgml/html/storage-hot.html --- postgresql-13-13.13/doc/src/sgml/html/storage-hot.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-hot.html 2024-02-05 22:04:29.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, @@ -42,4 +42,4 @@ 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.13/doc/src/sgml/html/storage-init.html postgresql-13-13.14/doc/src/sgml/html/storage-init.html --- postgresql-13-13.13/doc/src/sgml/html/storage-init.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-init.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/storage-page-layout.html postgresql-13-13.14/doc/src/sgml/html/storage-page-layout.html --- postgresql-13-13.13/doc/src/sgml/html/storage-page-layout.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-page-layout.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/storage-toast.html postgresql-13-13.14/doc/src/sgml/html/storage-toast.html --- postgresql-13-13.13/doc/src/sgml/html/storage-toast.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-toast.html 2024-02-05 22:04:28.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).

    @@ -216,4 +216,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.13/doc/src/sgml/html/storage-vm.html postgresql-13-13.14/doc/src/sgml/html/storage-vm.html --- postgresql-13-13.13/doc/src/sgml/html/storage-vm.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage-vm.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/storage.html postgresql-13-13.14/doc/src/sgml/html/storage.html --- postgresql-13-13.13/doc/src/sgml/html/storage.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/storage.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/supported-platforms.html postgresql-13-13.14/doc/src/sgml/html/supported-platforms.html --- postgresql-13-13.13/doc/src/sgml/html/supported-platforms.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/supported-platforms.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/system-catalog-declarations.html postgresql-13-13.14/doc/src/sgml/html/system-catalog-declarations.html --- postgresql-13-13.13/doc/src/sgml/html/system-catalog-declarations.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/system-catalog-declarations.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/system-catalog-initial-data.html postgresql-13-13.14/doc/src/sgml/html/system-catalog-initial-data.html --- postgresql-13-13.13/doc/src/sgml/html/system-catalog-initial-data.html 2023-11-06 22:30:50.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/system-catalog-initial-data.html 2024-02-05 22:04:29.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.13/doc/src/sgml/html/tableam.html postgresql-13-13.14/doc/src/sgml/html/tableam.html --- postgresql-13-13.13/doc/src/sgml/html/tableam.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tableam.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/tablefunc.html postgresql-13-13.14/doc/src/sgml/html/tablefunc.html --- postgresql-13-13.13/doc/src/sgml/html/tablefunc.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tablefunc.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/tablesample-method.html postgresql-13-13.14/doc/src/sgml/html/tablesample-method.html --- postgresql-13-13.13/doc/src/sgml/html/tablesample-method.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tablesample-method.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/tablesample-support-functions.html postgresql-13-13.14/doc/src/sgml/html/tablesample-support-functions.html --- postgresql-13-13.13/doc/src/sgml/html/tablesample-support-functions.html 2023-11-06 22:30:49.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tablesample-support-functions.html 2024-02-05 22:04:28.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.13/doc/src/sgml/html/tcn.html postgresql-13-13.14/doc/src/sgml/html/tcn.html --- postgresql-13-13.13/doc/src/sgml/html/tcn.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tcn.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/test-decoding.html postgresql-13-13.14/doc/src/sgml/html/test-decoding.html --- postgresql-13-13.13/doc/src/sgml/html/test-decoding.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/test-decoding.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/textsearch-configuration.html postgresql-13-13.14/doc/src/sgml/html/textsearch-configuration.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-configuration.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-configuration.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-controls.html postgresql-13-13.14/doc/src/sgml/html/textsearch-controls.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-controls.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-controls.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-debugging.html postgresql-13-13.14/doc/src/sgml/html/textsearch-debugging.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-debugging.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-debugging.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-dictionaries.html postgresql-13-13.14/doc/src/sgml/html/textsearch-dictionaries.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-dictionaries.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-dictionaries.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-features.html postgresql-13-13.14/doc/src/sgml/html/textsearch-features.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-features.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-features.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-indexes.html postgresql-13-13.14/doc/src/sgml/html/textsearch-indexes.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-indexes.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-indexes.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-intro.html postgresql-13-13.14/doc/src/sgml/html/textsearch-intro.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-intro.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-intro.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-limitations.html postgresql-13-13.14/doc/src/sgml/html/textsearch-limitations.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-limitations.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-limitations.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-parsers.html postgresql-13-13.14/doc/src/sgml/html/textsearch-parsers.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-parsers.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-parsers.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-psql.html postgresql-13-13.14/doc/src/sgml/html/textsearch-psql.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-psql.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-psql.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch-tables.html postgresql-13-13.14/doc/src/sgml/html/textsearch-tables.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch-tables.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch-tables.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/textsearch.html postgresql-13-13.14/doc/src/sgml/html/textsearch.html --- postgresql-13-13.13/doc/src/sgml/html/textsearch.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/textsearch.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/transaction-iso.html postgresql-13-13.14/doc/src/sgml/html/transaction-iso.html --- postgresql-13-13.13/doc/src/sgml/html/transaction-iso.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/transaction-iso.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/trigger-datachanges.html postgresql-13-13.14/doc/src/sgml/html/trigger-datachanges.html --- postgresql-13-13.13/doc/src/sgml/html/trigger-datachanges.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/trigger-datachanges.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/trigger-definition.html postgresql-13-13.14/doc/src/sgml/html/trigger-definition.html --- postgresql-13-13.13/doc/src/sgml/html/trigger-definition.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/trigger-definition.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/trigger-example.html postgresql-13-13.14/doc/src/sgml/html/trigger-example.html --- postgresql-13-13.13/doc/src/sgml/html/trigger-example.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/trigger-example.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/trigger-interface.html postgresql-13-13.14/doc/src/sgml/html/trigger-interface.html --- postgresql-13-13.13/doc/src/sgml/html/trigger-interface.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/trigger-interface.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/triggers.html postgresql-13-13.14/doc/src/sgml/html/triggers.html --- postgresql-13-13.13/doc/src/sgml/html/triggers.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/triggers.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/tsm-system-rows.html postgresql-13-13.14/doc/src/sgml/html/tsm-system-rows.html --- postgresql-13-13.13/doc/src/sgml/html/tsm-system-rows.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tsm-system-rows.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/tsm-system-time.html postgresql-13-13.14/doc/src/sgml/html/tsm-system-time.html --- postgresql-13-13.13/doc/src/sgml/html/tsm-system-time.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tsm-system-time.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/tutorial-accessdb.html postgresql-13-13.14/doc/src/sgml/html/tutorial-accessdb.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-accessdb.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-accessdb.html 2024-02-05 22:04:04.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.13)
+psql (13.14)
 Type "help" for help.
 
 mydb=>
@@ -63,7 +63,7 @@
 mydb=> SELECT version();
                                          version
 -------------------------------------------------------------------​-----------------------
- PostgreSQL 13.13 on x86_64-pc-linux-gnu, compiled by gcc (Debian 4.9.2-10) 4.9.2, 64-bit
+ PostgreSQL 13.14 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.13/doc/src/sgml/html/tutorial-advanced-intro.html postgresql-13-13.14/doc/src/sgml/html/tutorial-advanced-intro.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-advanced-intro.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-advanced-intro.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-advanced.html postgresql-13-13.14/doc/src/sgml/html/tutorial-advanced.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-advanced.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-advanced.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-agg.html postgresql-13-13.14/doc/src/sgml/html/tutorial-agg.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-agg.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-agg.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-arch.html postgresql-13-13.14/doc/src/sgml/html/tutorial-arch.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-arch.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-arch.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-concepts.html postgresql-13-13.14/doc/src/sgml/html/tutorial-concepts.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-concepts.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-concepts.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-conclusion.html postgresql-13-13.14/doc/src/sgml/html/tutorial-conclusion.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-conclusion.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-conclusion.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-createdb.html postgresql-13-13.14/doc/src/sgml/html/tutorial-createdb.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-createdb.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-createdb.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-delete.html postgresql-13-13.14/doc/src/sgml/html/tutorial-delete.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-delete.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-delete.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-fk.html postgresql-13-13.14/doc/src/sgml/html/tutorial-fk.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-fk.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-fk.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-inheritance.html postgresql-13-13.14/doc/src/sgml/html/tutorial-inheritance.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-inheritance.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-inheritance.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-install.html postgresql-13-13.14/doc/src/sgml/html/tutorial-install.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-install.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-install.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-join.html postgresql-13-13.14/doc/src/sgml/html/tutorial-join.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-join.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-join.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-populate.html postgresql-13-13.14/doc/src/sgml/html/tutorial-populate.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-populate.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-populate.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-select.html postgresql-13-13.14/doc/src/sgml/html/tutorial-select.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-select.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-select.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-sql-intro.html postgresql-13-13.14/doc/src/sgml/html/tutorial-sql-intro.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-sql-intro.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-sql-intro.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-sql.html postgresql-13-13.14/doc/src/sgml/html/tutorial-sql.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-sql.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-sql.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-start.html postgresql-13-13.14/doc/src/sgml/html/tutorial-start.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-start.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-start.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-table.html postgresql-13-13.14/doc/src/sgml/html/tutorial-table.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-table.html 2023-11-06 22:30:24.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-table.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-transactions.html postgresql-13-13.14/doc/src/sgml/html/tutorial-transactions.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-transactions.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-transactions.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-update.html postgresql-13-13.14/doc/src/sgml/html/tutorial-update.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-update.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-update.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-views.html postgresql-13-13.14/doc/src/sgml/html/tutorial-views.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-views.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-views.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial-window.html postgresql-13-13.14/doc/src/sgml/html/tutorial-window.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial-window.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial-window.html 2024-02-05 22:04:04.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.13/doc/src/sgml/html/tutorial.html postgresql-13-13.14/doc/src/sgml/html/tutorial.html --- postgresql-13-13.13/doc/src/sgml/html/tutorial.html 2023-11-06 22:30:25.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/tutorial.html 2024-02-05 22:04:04.000000000 +0000 @@ -1,5 +1,5 @@ -Part I. Tutorial
    Part I. Tutorial
    Prev UpPostgreSQL 13.13 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.13/doc/src/sgml/html/typeconv-func.html postgresql-13-13.14/doc/src/sgml/html/typeconv-func.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv-func.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv-func.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/typeconv-oper.html postgresql-13-13.14/doc/src/sgml/html/typeconv-oper.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv-oper.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv-oper.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/typeconv-overview.html postgresql-13-13.14/doc/src/sgml/html/typeconv-overview.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv-overview.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv-overview.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/typeconv-query.html postgresql-13-13.14/doc/src/sgml/html/typeconv-query.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv-query.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv-query.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/typeconv-select.html postgresql-13-13.14/doc/src/sgml/html/typeconv-select.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv-select.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv-select.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/typeconv-union-case.html postgresql-13-13.14/doc/src/sgml/html/typeconv-union-case.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv-union-case.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv-union-case.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/typeconv.html postgresql-13-13.14/doc/src/sgml/html/typeconv.html --- postgresql-13-13.13/doc/src/sgml/html/typeconv.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/typeconv.html 2024-02-05 22:04:08.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.13/doc/src/sgml/html/unaccent.html postgresql-13-13.14/doc/src/sgml/html/unaccent.html --- postgresql-13-13.13/doc/src/sgml/html/unaccent.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/unaccent.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/unsupported-features-sql-standard.html postgresql-13-13.14/doc/src/sgml/html/unsupported-features-sql-standard.html --- postgresql-13-13.13/doc/src/sgml/html/unsupported-features-sql-standard.html 2023-11-06 22:30:52.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/unsupported-features-sql-standard.html 2024-02-05 22:04:31.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.13/doc/src/sgml/html/upgrading.html postgresql-13-13.14/doc/src/sgml/html/upgrading.html --- postgresql-13-13.13/doc/src/sgml/html/upgrading.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/upgrading.html 2024-02-05 22:04:09.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.13, + command from PostgreSQL 13.14, 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.13/doc/src/sgml/html/user-manag.html postgresql-13-13.14/doc/src/sgml/html/user-manag.html --- postgresql-13-13.13/doc/src/sgml/html/user-manag.html 2023-11-06 22:30:31.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/user-manag.html 2024-02-05 22:04:10.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.13/doc/src/sgml/html/using-explain.html postgresql-13-13.14/doc/src/sgml/html/using-explain.html --- postgresql-13-13.13/doc/src/sgml/html/using-explain.html 2023-11-06 22:30:29.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/using-explain.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/uuid-ossp.html postgresql-13-13.14/doc/src/sgml/html/uuid-ossp.html --- postgresql-13-13.13/doc/src/sgml/html/uuid-ossp.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/uuid-ossp.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/vacuumlo.html postgresql-13-13.14/doc/src/sgml/html/vacuumlo.html --- postgresql-13-13.13/doc/src/sgml/html/vacuumlo.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/vacuumlo.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/view-pg-available-extension-versions.html postgresql-13-13.14/doc/src/sgml/html/view-pg-available-extension-versions.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-available-extension-versions.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-available-extension-versions.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-available-extensions.html postgresql-13-13.14/doc/src/sgml/html/view-pg-available-extensions.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-available-extensions.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-available-extensions.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-config.html postgresql-13-13.14/doc/src/sgml/html/view-pg-config.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-config.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-config.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-cursors.html postgresql-13-13.14/doc/src/sgml/html/view-pg-cursors.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-cursors.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-cursors.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-file-settings.html postgresql-13-13.14/doc/src/sgml/html/view-pg-file-settings.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-file-settings.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-file-settings.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-group.html postgresql-13-13.14/doc/src/sgml/html/view-pg-group.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-group.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-group.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-hba-file-rules.html postgresql-13-13.14/doc/src/sgml/html/view-pg-hba-file-rules.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-hba-file-rules.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-hba-file-rules.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-indexes.html postgresql-13-13.14/doc/src/sgml/html/view-pg-indexes.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-indexes.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-indexes.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-locks.html postgresql-13-13.14/doc/src/sgml/html/view-pg-locks.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-locks.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-locks.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-matviews.html postgresql-13-13.14/doc/src/sgml/html/view-pg-matviews.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-matviews.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-matviews.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-policies.html postgresql-13-13.14/doc/src/sgml/html/view-pg-policies.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-policies.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-policies.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-prepared-statements.html postgresql-13-13.14/doc/src/sgml/html/view-pg-prepared-statements.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-prepared-statements.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-prepared-statements.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-prepared-xacts.html postgresql-13-13.14/doc/src/sgml/html/view-pg-prepared-xacts.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-prepared-xacts.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-prepared-xacts.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-publication-tables.html postgresql-13-13.14/doc/src/sgml/html/view-pg-publication-tables.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-publication-tables.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-publication-tables.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-replication-origin-status.html postgresql-13-13.14/doc/src/sgml/html/view-pg-replication-origin-status.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-replication-origin-status.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-replication-origin-status.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-replication-slots.html postgresql-13-13.14/doc/src/sgml/html/view-pg-replication-slots.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-replication-slots.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-replication-slots.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-roles.html postgresql-13-13.14/doc/src/sgml/html/view-pg-roles.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-roles.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-roles.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-rules.html postgresql-13-13.14/doc/src/sgml/html/view-pg-rules.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-rules.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-rules.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-seclabels.html postgresql-13-13.14/doc/src/sgml/html/view-pg-seclabels.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-seclabels.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-seclabels.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-sequences.html postgresql-13-13.14/doc/src/sgml/html/view-pg-sequences.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-sequences.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-sequences.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-settings.html postgresql-13-13.14/doc/src/sgml/html/view-pg-settings.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-settings.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-settings.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-shadow.html postgresql-13-13.14/doc/src/sgml/html/view-pg-shadow.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-shadow.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-shadow.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-shmem-allocations.html postgresql-13-13.14/doc/src/sgml/html/view-pg-shmem-allocations.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-shmem-allocations.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-shmem-allocations.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-stats-ext.html postgresql-13-13.14/doc/src/sgml/html/view-pg-stats-ext.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-stats-ext.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-stats-ext.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-stats.html postgresql-13-13.14/doc/src/sgml/html/view-pg-stats.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-stats.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-stats.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-tables.html postgresql-13-13.14/doc/src/sgml/html/view-pg-tables.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-tables.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-tables.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-timezone-abbrevs.html postgresql-13-13.14/doc/src/sgml/html/view-pg-timezone-abbrevs.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-timezone-abbrevs.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-timezone-abbrevs.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-timezone-names.html postgresql-13-13.14/doc/src/sgml/html/view-pg-timezone-names.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-timezone-names.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-timezone-names.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-user-mappings.html postgresql-13-13.14/doc/src/sgml/html/view-pg-user-mappings.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-user-mappings.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-user-mappings.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-user.html postgresql-13-13.14/doc/src/sgml/html/view-pg-user.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-user.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-user.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/view-pg-views.html postgresql-13-13.14/doc/src/sgml/html/view-pg-views.html --- postgresql-13-13.13/doc/src/sgml/html/view-pg-views.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/view-pg-views.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/views-overview.html postgresql-13-13.14/doc/src/sgml/html/views-overview.html --- postgresql-13-13.13/doc/src/sgml/html/views-overview.html 2023-11-06 22:30:48.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/views-overview.html 2024-02-05 22:04:27.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.13/doc/src/sgml/html/wal-async-commit.html postgresql-13-13.14/doc/src/sgml/html/wal-async-commit.html --- postgresql-13-13.13/doc/src/sgml/html/wal-async-commit.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/wal-async-commit.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/wal-configuration.html postgresql-13-13.14/doc/src/sgml/html/wal-configuration.html --- postgresql-13-13.13/doc/src/sgml/html/wal-configuration.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/wal-configuration.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/wal-internals.html postgresql-13-13.14/doc/src/sgml/html/wal-internals.html --- postgresql-13-13.13/doc/src/sgml/html/wal-internals.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/wal-internals.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/wal-intro.html postgresql-13-13.14/doc/src/sgml/html/wal-intro.html --- postgresql-13-13.13/doc/src/sgml/html/wal-intro.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/wal-intro.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/wal-reliability.html postgresql-13-13.14/doc/src/sgml/html/wal-reliability.html --- postgresql-13-13.13/doc/src/sgml/html/wal-reliability.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/wal-reliability.html 2024-02-05 22:04:12.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 @@ -57,7 +57,7 @@ to disable it.

  • On FreeBSD, IDE drives can be queried using - atacontrol and write caching turned off using + camcontrol identify and write caching turned off using hw.ata.wc=0 in /boot/loader.conf; SCSI drives can be queried using camcontrol identify, and the write cache both queried and changed using @@ -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.13/doc/src/sgml/html/wal.html postgresql-13-13.14/doc/src/sgml/html/wal.html --- postgresql-13-13.13/doc/src/sgml/html/wal.html 2023-11-06 22:30:33.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/wal.html 2024-02-05 22:04:12.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.13/doc/src/sgml/html/warm-standby-failover.html postgresql-13-13.14/doc/src/sgml/html/warm-standby-failover.html --- postgresql-13-13.13/doc/src/sgml/html/warm-standby-failover.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/warm-standby-failover.html 2024-02-05 22:04:11.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.13/doc/src/sgml/html/warm-standby.html postgresql-13-13.14/doc/src/sgml/html/warm-standby.html --- postgresql-13-13.13/doc/src/sgml/html/warm-standby.html 2023-11-06 22:30:32.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/warm-standby.html 2024-02-05 22:04:11.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 @@ -103,7 +103,7 @@ later disconnected, the standby goes back to step 1 and tries to restore the file from the archive again. This loop of retries from the archive, pg_wal, and via streaming replication goes on until the server - is stopped or failover is triggered by a trigger file. + is stopped or is promoted.

    Standby mode is exited and the server switches to normal operation when pg_ctl promote is run, @@ -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.13/doc/src/sgml/html/when-can-parallel-query-be-used.html postgresql-13-13.14/doc/src/sgml/html/when-can-parallel-query-be-used.html --- postgresql-13-13.13/doc/src/sgml/html/when-can-parallel-query-be-used.html 2023-11-06 22:30:30.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/when-can-parallel-query-be-used.html 2024-02-05 22:04:09.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.13/doc/src/sgml/html/xaggr.html postgresql-13-13.14/doc/src/sgml/html/xaggr.html --- postgresql-13-13.13/doc/src/sgml/html/xaggr.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xaggr.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-c.html postgresql-13-13.14/doc/src/sgml/html/xfunc-c.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-c.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-c.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-internal.html postgresql-13-13.14/doc/src/sgml/html/xfunc-internal.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-internal.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-internal.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-optimization.html postgresql-13-13.14/doc/src/sgml/html/xfunc-optimization.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-optimization.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-optimization.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-overload.html postgresql-13-13.14/doc/src/sgml/html/xfunc-overload.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-overload.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-overload.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-pl.html postgresql-13-13.14/doc/src/sgml/html/xfunc-pl.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-pl.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-pl.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-sql.html postgresql-13-13.14/doc/src/sgml/html/xfunc-sql.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-sql.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-sql.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc-volatility.html postgresql-13-13.14/doc/src/sgml/html/xfunc-volatility.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc-volatility.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc-volatility.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xfunc.html postgresql-13-13.14/doc/src/sgml/html/xfunc.html --- postgresql-13-13.13/doc/src/sgml/html/xfunc.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xfunc.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xindex.html postgresql-13-13.14/doc/src/sgml/html/xindex.html --- postgresql-13-13.13/doc/src/sgml/html/xindex.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xindex.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xml-limits-conformance.html postgresql-13-13.14/doc/src/sgml/html/xml-limits-conformance.html --- postgresql-13-13.13/doc/src/sgml/html/xml-limits-conformance.html 2023-11-06 22:30:53.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xml-limits-conformance.html 2024-02-05 22:04:31.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.13/doc/src/sgml/html/xml2.html postgresql-13-13.14/doc/src/sgml/html/xml2.html --- postgresql-13-13.13/doc/src/sgml/html/xml2.html 2023-11-06 22:30:54.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xml2.html 2024-02-05 22:04:33.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.13/doc/src/sgml/html/xoper-optimization.html postgresql-13-13.14/doc/src/sgml/html/xoper-optimization.html --- postgresql-13-13.13/doc/src/sgml/html/xoper-optimization.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xoper-optimization.html 2024-02-05 22:04:15.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.13 understands. + the ones that release 13.14 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.13/doc/src/sgml/html/xoper.html postgresql-13-13.14/doc/src/sgml/html/xoper.html --- postgresql-13-13.13/doc/src/sgml/html/xoper.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xoper.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xplang-install.html postgresql-13-13.14/doc/src/sgml/html/xplang-install.html --- postgresql-13-13.13/doc/src/sgml/html/xplang-install.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xplang-install.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xplang.html postgresql-13-13.14/doc/src/sgml/html/xplang.html --- postgresql-13-13.13/doc/src/sgml/html/xplang.html 2023-11-06 22:30:37.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xplang.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xproc.html postgresql-13-13.14/doc/src/sgml/html/xproc.html --- postgresql-13-13.13/doc/src/sgml/html/xproc.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xproc.html 2024-02-05 22:04:15.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.13/doc/src/sgml/html/xtypes.html postgresql-13-13.14/doc/src/sgml/html/xtypes.html --- postgresql-13-13.13/doc/src/sgml/html/xtypes.html 2023-11-06 22:30:36.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/html/xtypes.html 2024-02-05 22:04:15.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.13/doc/src/sgml/indices.sgml postgresql-13-13.14/doc/src/sgml/indices.sgml --- postgresql-13-13.13/doc/src/sgml/indices.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/indices.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -91,6 +91,39 @@     + In general, PostgreSQL indexes can be used + to optimize queries that contain one or more WHERE + or JOIN clauses of the form + + +indexed-column indexable-operator comparison-value + + + Here, the indexed-column is whatever + column or expression the index has been defined on. + The indexable-operator is an operator that + is a member of the index's operator class for + the indexed column. (More details about that appear below.) + And the comparison-value can be any + expression that is not volatile and does not reference the index's + table. + + + + In some cases the query planner can extract an indexable clause of + this form from another SQL construct. A simple example is that if + the original clause was + + +comparison-value operator indexed-column + + + then it can be flipped around into indexable form if the + original operator has a commutator + operator that is a member of the index's operator class. + + + Creating an index on a large table can take a long time. By default, PostgreSQL allows reads (SELECT statements) to occur on the table in parallel with index creation, but writes (INSERT, @@ -120,7 +153,7 @@ B-tree, Hash, GiST, SP-GiST, GIN, BRIN, and the extension bloom. Each index type uses a different - algorithm that is best suited to different types of queries. + algorithm that is best suited to different types of indexable clauses. By default, the CREATE INDEX command creates B-tree indexes, which fit the most common situations. diff -Nru postgresql-13-13.13/doc/src/sgml/information_schema.sgml postgresql-13-13.14/doc/src/sgml/information_schema.sgml --- postgresql-13-13.13/doc/src/sgml/information_schema.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/information_schema.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -697,8 +697,8 @@ An encoding of some character repertoire. Most older character repertoires only use one encoding form, and so there are no - separate names for them (e.g., LATIN1 is an - encoding form applicable to the LATIN1 + separate names for them (e.g., LATIN2 is an + encoding form applicable to the LATIN2 repertoire). But for example Unicode has the encoding forms UTF8, UTF16, etc. (not all supported by PostgreSQL). Encoding forms are not exposed diff -Nru postgresql-13-13.13/doc/src/sgml/legal.sgml postgresql-13-13.14/doc/src/sgml/legal.sgml --- postgresql-13-13.13/doc/src/sgml/legal.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/legal.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1,9 +1,9 @@ -2023 +2024 - 1996–2023 + 1996–2024 The PostgreSQL Global Development Group @@ -11,7 +11,7 @@ Legal Notice - PostgreSQL is Copyright © 1996–2023 + PostgreSQL is Copyright © 1996–2024 by the PostgreSQL Global Development Group. diff -Nru postgresql-13-13.13/doc/src/sgml/libpq.sgml postgresql-13-13.14/doc/src/sgml/libpq.sgml --- postgresql-13-13.13/doc/src/sgml/libpq.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/libpq.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -4790,11 +4790,12 @@ - In the nonblocking state, calls to + In the nonblocking state, successful calls to , , , , - and will not block but instead return - an error if they need to be called again. + and will not block; their changes + are stored in the local output buffer until they are flushed. + Unsuccessful calls will return an error and must be retried. diff -Nru postgresql-13-13.13/doc/src/sgml/logical-replication.sgml postgresql-13-13.14/doc/src/sgml/logical-replication.sgml --- postgresql-13-13.13/doc/src/sgml/logical-replication.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/logical-replication.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -442,7 +442,8 @@ implemented by walsender and apply processes. The walsender process starts logical decoding (described in ) of the WAL and loads the standard - logical decoding plugin (pgoutput). The plugin transforms the changes read + logical decoding output plugin (pgoutput). The plugin + transforms the changes read from WAL to the logical replication protocol (see ) and filters the data according to the publication specification. The data is then continuously diff -Nru postgresql-13-13.13/doc/src/sgml/man1/clusterdb.1 postgresql-13-13.14/doc/src/sgml/man1/clusterdb.1 --- postgresql-13-13.13/doc/src/sgml/man1/clusterdb.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/clusterdb.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: clusterdb .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CLUSTERDB" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CLUSTERDB" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/createdb.1 postgresql-13-13.14/doc/src/sgml/man1/createdb.1 --- postgresql-13-13.13/doc/src/sgml/man1/createdb.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/createdb.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: createdb .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATEDB" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATEDB" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/createuser.1 postgresql-13-13.14/doc/src/sgml/man1/createuser.1 --- postgresql-13-13.13/doc/src/sgml/man1/createuser.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/createuser.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: createuser .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATEUSER" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATEUSER" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/dropdb.1 postgresql-13-13.14/doc/src/sgml/man1/dropdb.1 --- postgresql-13-13.13/doc/src/sgml/man1/dropdb.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/dropdb.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dropdb .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROPDB" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROPDB" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/dropuser.1 postgresql-13-13.14/doc/src/sgml/man1/dropuser.1 --- postgresql-13-13.13/doc/src/sgml/man1/dropuser.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/dropuser.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dropuser .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROPUSER" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROPUSER" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/ecpg.1 postgresql-13-13.14/doc/src/sgml/man1/ecpg.1 --- postgresql-13-13.13/doc/src/sgml/man1/ecpg.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/ecpg.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ecpg .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ECPG" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ECPG" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/initdb.1 postgresql-13-13.14/doc/src/sgml/man1/initdb.1 --- postgresql-13-13.13/doc/src/sgml/man1/initdb.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/initdb.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: initdb .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "INITDB" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "INITDB" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/oid2name.1 postgresql-13-13.14/doc/src/sgml/man1/oid2name.1 --- postgresql-13-13.13/doc/src/sgml/man1/oid2name.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/oid2name.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: oid2name .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "OID2NAME" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "OID2NAME" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_archivecleanup.1 postgresql-13-13.14/doc/src/sgml/man1/pg_archivecleanup.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_archivecleanup.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_archivecleanup.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_archivecleanup .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_ARCHIVECLEANUP" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_ARCHIVECLEANUP" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_basebackup.1 postgresql-13-13.14/doc/src/sgml/man1/pg_basebackup.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_basebackup.1 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_basebackup.1 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_basebackup .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_BASEBACKUP" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_BASEBACKUP" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_checksums.1 postgresql-13-13.14/doc/src/sgml/man1/pg_checksums.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_checksums.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_checksums.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_checksums .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_CHECKSUMS" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_CHECKSUMS" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_config.1 postgresql-13-13.14/doc/src/sgml/man1/pg_config.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_config.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_config.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_config .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_CONFIG" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_CONFIG" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_controldata.1 postgresql-13-13.14/doc/src/sgml/man1/pg_controldata.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_controldata.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_controldata.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_controldata .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_CONTROLDATA" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_CONTROLDATA" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_ctl.1 postgresql-13-13.14/doc/src/sgml/man1/pg_ctl.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_ctl.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_ctl.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_ctl .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_CTL" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_CTL" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_dump.1 postgresql-13-13.14/doc/src/sgml/man1/pg_dump.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_dump.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_dump.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_dump .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_DUMP" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_DUMP" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_dumpall.1 postgresql-13-13.14/doc/src/sgml/man1/pg_dumpall.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_dumpall.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_dumpall.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_dumpall .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_DUMPALL" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_DUMPALL" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_isready.1 postgresql-13-13.14/doc/src/sgml/man1/pg_isready.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_isready.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_isready.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_isready .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_ISREADY" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_ISREADY" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_receivewal.1 postgresql-13-13.14/doc/src/sgml/man1/pg_receivewal.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_receivewal.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_receivewal.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_receivewal .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_RECEIVEWAL" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_RECEIVEWAL" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_recvlogical.1 postgresql-13-13.14/doc/src/sgml/man1/pg_recvlogical.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_recvlogical.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_recvlogical.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_recvlogical .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_RECVLOGICAL" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_RECVLOGICAL" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_resetwal.1 postgresql-13-13.14/doc/src/sgml/man1/pg_resetwal.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_resetwal.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_resetwal.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_resetwal .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_RESETWAL" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_RESETWAL" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_restore.1 postgresql-13-13.14/doc/src/sgml/man1/pg_restore.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_restore.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_restore.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_restore .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_RESTORE" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_RESTORE" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_rewind.1 postgresql-13-13.14/doc/src/sgml/man1/pg_rewind.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_rewind.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_rewind.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_rewind .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_REWIND" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_REWIND" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_standby.1 postgresql-13-13.14/doc/src/sgml/man1/pg_standby.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_standby.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_standby.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_standby .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_STANDBY" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_STANDBY" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_test_fsync.1 postgresql-13-13.14/doc/src/sgml/man1/pg_test_fsync.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_test_fsync.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_test_fsync.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_test_fsync .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_TEST_FSYNC" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_TEST_FSYNC" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_test_timing.1 postgresql-13-13.14/doc/src/sgml/man1/pg_test_timing.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_test_timing.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_test_timing.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_test_timing .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_TEST_TIMING" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_TEST_TIMING" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_upgrade.1 postgresql-13-13.14/doc/src/sgml/man1/pg_upgrade.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_upgrade.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_upgrade.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_upgrade .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_UPGRADE" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_UPGRADE" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_verifybackup.1 postgresql-13-13.14/doc/src/sgml/man1/pg_verifybackup.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_verifybackup.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_verifybackup.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_verifybackup .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_VERIFYBACKUP" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_VERIFYBACKUP" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pg_waldump.1 postgresql-13-13.14/doc/src/sgml/man1/pg_waldump.1 --- postgresql-13-13.13/doc/src/sgml/man1/pg_waldump.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pg_waldump.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pg_waldump .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PG_WALDUMP" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PG_WALDUMP" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/pgbench.1 postgresql-13-13.14/doc/src/sgml/man1/pgbench.1 --- postgresql-13-13.13/doc/src/sgml/man1/pgbench.1 2023-11-06 22:31:04.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/pgbench.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: pgbench .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PGBENCH" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PGBENCH" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/postgres.1 postgresql-13-13.14/doc/src/sgml/man1/postgres.1 --- postgresql-13-13.13/doc/src/sgml/man1/postgres.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/postgres.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: postgres .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "POSTGRES" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "POSTGRES" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/postmaster.1 postgresql-13-13.14/doc/src/sgml/man1/postmaster.1 --- postgresql-13-13.13/doc/src/sgml/man1/postmaster.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/postmaster.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: postmaster .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "POSTMASTER" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "POSTMASTER" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/psql.1 postgresql-13-13.14/doc/src/sgml/man1/psql.1 --- postgresql-13-13.13/doc/src/sgml/man1/psql.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/psql.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: psql .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PSQL" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PSQL" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -655,7 +655,7 @@ .\} .nf $ \fBpsql testdb\fR -psql (13\&.13) +psql (13\&.14) Type "help" for help\&. testdb=> diff -Nru postgresql-13-13.13/doc/src/sgml/man1/reindexdb.1 postgresql-13-13.14/doc/src/sgml/man1/reindexdb.1 --- postgresql-13-13.13/doc/src/sgml/man1/reindexdb.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/reindexdb.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: reindexdb .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "REINDEXDB" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "REINDEXDB" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/vacuumdb.1 postgresql-13-13.14/doc/src/sgml/man1/vacuumdb.1 --- postgresql-13-13.13/doc/src/sgml/man1/vacuumdb.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/vacuumdb.1 2024-02-05 22:04:43.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: vacuumdb .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "VACUUMDB" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "VACUUMDB" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man1/vacuumlo.1 postgresql-13-13.14/doc/src/sgml/man1/vacuumlo.1 --- postgresql-13-13.13/doc/src/sgml/man1/vacuumlo.1 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man1/vacuumlo.1 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: vacuumlo .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "VACUUMLO" "1" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "VACUUMLO" "1" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_commit.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_commit.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_commit.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_commit.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_commit .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_COMMIT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_COMMIT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_connect.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_connect.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_connect.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_connect.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_connect .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CONNECT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CONNECT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_copytuple.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_copytuple.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_copytuple.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_copytuple.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_copytuple .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_COPYTUPLE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_COPYTUPLE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_close.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_close.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_close.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_close.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_close .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_CLOSE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_CLOSE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_fetch.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_fetch.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_fetch.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_fetch.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_fetch .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_FETCH" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_FETCH" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_find.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_find.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_find.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_find.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_find .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_FIND" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_FIND" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_move.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_move.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_move.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_move.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_move .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_MOVE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_MOVE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_open.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_open.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_open.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_open.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_open .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_OPEN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_OPEN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_open_with_args.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_open_with_args.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_open_with_args.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_open_with_args.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_open_with_args .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_OPEN_WITH_ARGS" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_OPEN_WITH_ARGS" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_cursor_open_with_paramlist.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_cursor_open_with_paramlist .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_CURSOR_OPEN_WITH_PARAMLIST" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_CURSOR_OPEN_WITH_PARAMLIST" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_exec.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_exec.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_exec.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_exec.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_exec .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_EXEC" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_EXEC" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_execp.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_execp.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_execp.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_execp.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_execp .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_EXECP" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_EXECP" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_execute.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_execute.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_execute.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_execute.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_execute .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_EXECUTE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_EXECUTE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_execute_plan.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_execute_plan.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_execute_plan.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_execute_plan.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_execute_plan .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_EXECUTE_PLAN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_EXECUTE_PLAN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_execute_plan_with_paramlist.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_execute_plan_with_paramlist .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_EXECUTE_PLAN_WITH_PARAMLIST" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_EXECUTE_PLAN_WITH_PARAMLIST" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_execute_with_args.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_execute_with_args.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_execute_with_args.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_execute_with_args.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_execute_with_args .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_EXECUTE_WITH_ARGS" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_EXECUTE_WITH_ARGS" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_finish.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_finish.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_finish.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_finish.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_finish .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_FINISH" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_FINISH" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_fname.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_fname.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_fname.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_fname.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_fname .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_FNAME" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_FNAME" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_fnumber.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_fnumber.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_fnumber.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_fnumber.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_fnumber .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_FNUMBER" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_FNUMBER" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_freeplan.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_freeplan.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_freeplan.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_freeplan.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_freeplan .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_FREEPLAN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_FREEPLAN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_freetuple.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_freetuple.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_freetuple.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_freetuple.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_freetuple .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_FREETUPLE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_FREETUPLE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_freetuptable.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_freetuptable.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_freetuptable.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_freetuptable.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_freetuptable .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_FREETUPTABLE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_FREETUPTABLE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_getargcount.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_getargcount.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_getargcount.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_getargcount.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_getargcount .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETARGCOUNT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETARGCOUNT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_getargtypeid.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_getargtypeid.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_getargtypeid.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_getargtypeid.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_getargtypeid .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETARGTYPEID" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETARGTYPEID" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_getbinval.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_getbinval.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_getbinval.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_getbinval.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_getbinval .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETBINVAL" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETBINVAL" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_getnspname.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_getnspname.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_getnspname.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_getnspname.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_getnspname .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETNSPNAME" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETNSPNAME" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_getrelname.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_getrelname.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_getrelname.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_getrelname.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_getrelname .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETRELNAME" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETRELNAME" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_gettype.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_gettype.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_gettype.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_gettype.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_gettype .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETTYPE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETTYPE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_gettypeid.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_gettypeid.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_gettypeid.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_gettypeid.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_gettypeid .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETTYPEID" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETTYPEID" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_getvalue.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_getvalue.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_getvalue.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_getvalue.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_getvalue .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_GETVALUE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_GETVALUE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_is_cursor_plan.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_is_cursor_plan.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_is_cursor_plan.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_is_cursor_plan.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_is_cursor_plan .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_IS_CURSOR_PLAN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_IS_CURSOR_PLAN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_keepplan.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_keepplan.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_keepplan.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_keepplan.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_keepplan .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_KEEPPLAN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_KEEPPLAN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_modifytuple.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_modifytuple.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_modifytuple.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_modifytuple.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_modifytuple .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_MODIFYTUPLE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_MODIFYTUPLE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_palloc.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_palloc.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_palloc.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_palloc.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_palloc .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_PALLOC" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_PALLOC" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_pfree.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_pfree.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_pfree.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_pfree.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_pfree .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_PFREE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_PFREE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_prepare.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_prepare.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_prepare.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_prepare.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_prepare .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_PREPARE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_PREPARE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_prepare_cursor.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_prepare_cursor.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_prepare_cursor.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_prepare_cursor.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_prepare_cursor .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_PREPARE_CURSOR" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_PREPARE_CURSOR" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_prepare_params.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_prepare_params.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_prepare_params.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_prepare_params.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_prepare_params .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_PREPARE_PARAMS" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_PREPARE_PARAMS" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_register_relation.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_register_relation.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_register_relation.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_register_relation.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_register_relation .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_REGISTER_RELATION" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_REGISTER_RELATION" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_register_trigger_data.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_register_trigger_data.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_register_trigger_data.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_register_trigger_data.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_register_trigger_data .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_REGISTER_TRIGGER_DATA" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_REGISTER_TRIGGER_DATA" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_repalloc.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_repalloc.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_repalloc.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_repalloc.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_repalloc .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_REPALLOC" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_REPALLOC" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_result_code_string.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_result_code_string.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_result_code_string.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_result_code_string.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_result_code_string .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_RESULT_CODE_STRING" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_RESULT_CODE_STRING" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_returntuple.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_returntuple.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_returntuple.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_returntuple.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_returntuple .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_RETURNTUPLE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_RETURNTUPLE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_rollback.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_rollback.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_rollback.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_rollback.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_rollback .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_ROLLBACK" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_ROLLBACK" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_saveplan.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_saveplan.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_saveplan.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_saveplan.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_saveplan .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_SAVEPLAN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_SAVEPLAN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_scroll_cursor_fetch.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_scroll_cursor_fetch .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_SCROLL_CURSOR_FETCH" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_SCROLL_CURSOR_FETCH" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_scroll_cursor_move.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_scroll_cursor_move.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_scroll_cursor_move.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_scroll_cursor_move.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_scroll_cursor_move .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_SCROLL_CURSOR_MOVE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_SCROLL_CURSOR_MOVE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_start_transaction.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_start_transaction.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_start_transaction.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_start_transaction.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_start_transaction .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_START_TRANSACTION" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_START_TRANSACTION" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/SPI_unregister_relation.3 postgresql-13-13.14/doc/src/sgml/man3/SPI_unregister_relation.3 --- postgresql-13-13.13/doc/src/sgml/man3/SPI_unregister_relation.3 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/SPI_unregister_relation.3 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SPI_unregister_relation .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SPI_UNREGISTER_RELATION" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SPI_UNREGISTER_RELATION" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink.3 postgresql-13-13.14/doc/src/sgml/man3/dblink.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_build_sql_delete.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_build_sql_delete.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_build_sql_delete.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_build_sql_delete.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_build_sql_delete .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_BUILD_SQL_DELETE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_BUILD_SQL_DELETE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_build_sql_insert.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_build_sql_insert.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_build_sql_insert.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_build_sql_insert.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_build_sql_insert .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_BUILD_SQL_INSERT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_BUILD_SQL_INSERT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_build_sql_update.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_build_sql_update.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_build_sql_update.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_build_sql_update.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_build_sql_update .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_BUILD_SQL_UPDATE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_BUILD_SQL_UPDATE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_cancel_query.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_cancel_query.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_cancel_query.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_cancel_query.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_cancel_query .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_CANCEL_QUERY" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_CANCEL_QUERY" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_close.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_close.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_close.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_close.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_close .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_CLOSE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_CLOSE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_connect.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_connect.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_connect.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_connect.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_connect .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_CONNECT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_CONNECT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_connect_u.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_connect_u.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_connect_u.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_connect_u.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_connect_u .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_CONNECT_U" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_CONNECT_U" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_disconnect.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_disconnect.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_disconnect.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_disconnect.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_disconnect .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_DISCONNECT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_DISCONNECT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_error_message.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_error_message.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_error_message.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_error_message.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_error_message .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_ERROR_MESSAGE" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_ERROR_MESSAGE" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_exec.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_exec.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_exec.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_exec.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_exec .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_EXEC" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_EXEC" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_fetch.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_fetch.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_fetch.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_fetch.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_fetch .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_FETCH" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_FETCH" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_get_connections.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_get_connections.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_get_connections.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_get_connections.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_get_connections .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_GET_CONNECTIONS" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_GET_CONNECTIONS" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_get_notify.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_get_notify.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_get_notify.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_get_notify.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_get_notify .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_GET_NOTIFY" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_GET_NOTIFY" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_get_pkey.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_get_pkey.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_get_pkey.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_get_pkey.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_get_pkey .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_GET_PKEY" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_GET_PKEY" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_get_result.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_get_result.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_get_result.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_get_result.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_get_result .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_GET_RESULT" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_GET_RESULT" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_is_busy.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_is_busy.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_is_busy.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_is_busy.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_is_busy .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_IS_BUSY" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_IS_BUSY" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_open.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_open.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_open.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_open.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_open .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_OPEN" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_OPEN" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man3/dblink_send_query.3 postgresql-13-13.14/doc/src/sgml/man3/dblink_send_query.3 --- postgresql-13-13.13/doc/src/sgml/man3/dblink_send_query.3 2023-11-06 22:31:05.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man3/dblink_send_query.3 2024-02-05 22:04:44.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: dblink_send_query .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DBLINK_SEND_QUERY" "3" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DBLINK_SEND_QUERY" "3" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ABORT.7 postgresql-13-13.14/doc/src/sgml/man7/ABORT.7 --- postgresql-13-13.13/doc/src/sgml/man7/ABORT.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ABORT.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ABORT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ABORT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ABORT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_AGGREGATE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_AGGREGATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_AGGREGATE.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_AGGREGATE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER AGGREGATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER AGGREGATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER AGGREGATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_COLLATION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_COLLATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_COLLATION.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_COLLATION.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER COLLATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER COLLATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER COLLATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_CONVERSION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_CONVERSION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_CONVERSION.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_CONVERSION.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER CONVERSION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER CONVERSION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER CONVERSION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_DATABASE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_DATABASE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_DATABASE.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_DATABASE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER DATABASE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER DATABASE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER DATABASE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_DEFAULT_PRIVILEGES.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER DEFAULT PRIVILEGES .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER DEFAULT PRIVILEGES" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER DEFAULT PRIVILEGES" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_DOMAIN.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_DOMAIN.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_DOMAIN.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_DOMAIN.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER DOMAIN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER DOMAIN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER DOMAIN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_EVENT_TRIGGER.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER EVENT TRIGGER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER EVENT TRIGGER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER EVENT TRIGGER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -60,7 +60,7 @@ The new name of the event trigger\&. .RE .PP -DISABLE/ENABLE [ REPLICA | ALWAYS ] TRIGGER +DISABLE/ENABLE [ REPLICA | ALWAYS ] .RS 4 These forms configure the firing of event triggers\&. A disabled trigger is still known to the system, but is not executed when its triggering event occurs\&. See also session_replication_role\&. diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_EXTENSION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_EXTENSION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_EXTENSION.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_EXTENSION.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER EXTENSION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER EXTENSION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER EXTENSION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_FOREIGN_DATA_WRAPPER.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER FOREIGN DATA WRAPPER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER FOREIGN DATA WRAPPER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -111,7 +111,7 @@ .RS 4 .\} .nf -ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo \*(Aq1\*(Aq, DROP \*(Aqbar\*(Aq); +ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo \*(Aq1\*(Aq, DROP bar); .fi .if n \{\ .RE diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_FOREIGN_TABLE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER FOREIGN TABLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER FOREIGN TABLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER FOREIGN TABLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_FUNCTION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_FUNCTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_FUNCTION.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_FUNCTION.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER FUNCTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER FUNCTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER FUNCTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_GROUP.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_GROUP.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_GROUP.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_GROUP.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER GROUP .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER GROUP" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER GROUP" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_INDEX.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_INDEX.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_INDEX.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_INDEX.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER INDEX .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER INDEX" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER INDEX" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_LANGUAGE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_LANGUAGE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_LANGUAGE.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_LANGUAGE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER LANGUAGE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER LANGUAGE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER LANGUAGE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 2023-11-06 22:31:00.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_LARGE_OBJECT.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER LARGE OBJECT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER LARGE OBJECT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER LARGE OBJECT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_MATERIALIZED_VIEW.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER MATERIALIZED VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER MATERIALIZED VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_OPERATOR.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_OPERATOR.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_OPERATOR.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_OPERATOR.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER OPERATOR .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER OPERATOR" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER OPERATOR" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_OPERATOR_CLASS.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER OPERATOR CLASS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER OPERATOR CLASS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER OPERATOR CLASS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_OPERATOR_FAMILY.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER OPERATOR FAMILY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER OPERATOR FAMILY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_POLICY.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_POLICY.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_POLICY.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_POLICY.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER POLICY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER POLICY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER POLICY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_PROCEDURE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_PROCEDURE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_PROCEDURE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_PROCEDURE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER PROCEDURE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER PROCEDURE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER PROCEDURE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_PUBLICATION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_PUBLICATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_PUBLICATION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_PUBLICATION.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER PUBLICATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER PUBLICATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER PUBLICATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_ROLE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_ROLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_ROLE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_ROLE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER ROLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER ROLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER ROLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_ROUTINE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_ROUTINE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_ROUTINE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_ROUTINE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER ROUTINE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER ROUTINE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER ROUTINE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_RULE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_RULE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_RULE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_RULE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER RULE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER RULE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER RULE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_SCHEMA.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_SCHEMA.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_SCHEMA.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_SCHEMA.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER SCHEMA .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER SCHEMA" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER SCHEMA" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_SEQUENCE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_SEQUENCE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_SEQUENCE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_SEQUENCE.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER SEQUENCE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER SEQUENCE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER SEQUENCE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_SERVER.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_SERVER.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_SERVER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_SERVER.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER SERVER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER SERVER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER SERVER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_STATISTICS.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_STATISTICS.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_STATISTICS.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_STATISTICS.7 2024-02-05 22:04:39.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER STATISTICS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER STATISTICS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER STATISTICS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_SUBSCRIPTION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER SUBSCRIPTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER SUBSCRIPTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER SUBSCRIPTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_SYSTEM.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_SYSTEM.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_SYSTEM.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_SYSTEM.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER SYSTEM .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER SYSTEM" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER SYSTEM" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TABLE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TABLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TABLE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TABLE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TABLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TABLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TABLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TABLESPACE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TABLESPACE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TABLESPACE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TABLESPACE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TABLESPACE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TABLESPACE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TABLESPACE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_CONFIGURATION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TEXT SEARCH CONFIGURATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TEXT SEARCH CONFIGURATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_DICTIONARY.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TEXT SEARCH DICTIONARY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TEXT SEARCH DICTIONARY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_PARSER.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TEXT SEARCH PARSER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TEXT SEARCH PARSER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TEXT_SEARCH_TEMPLATE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TEXT SEARCH TEMPLATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TEXT SEARCH TEMPLATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TRIGGER.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TRIGGER.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TRIGGER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TRIGGER.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TRIGGER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TRIGGER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TRIGGER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_TYPE.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_TYPE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_TYPE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_TYPE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER TYPE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER TYPE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER TYPE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_USER.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_USER.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_USER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_USER.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER USER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER USER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER USER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_USER_MAPPING.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_USER_MAPPING.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_USER_MAPPING.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_USER_MAPPING.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER USER MAPPING .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER USER MAPPING" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER USER MAPPING" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ALTER_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/ALTER_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/ALTER_VIEW.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ALTER_VIEW.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ALTER VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ALTER VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ALTER VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ANALYZE.7 postgresql-13-13.14/doc/src/sgml/man7/ANALYZE.7 --- postgresql-13-13.13/doc/src/sgml/man7/ANALYZE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ANALYZE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ANALYZE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ANALYZE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ANALYZE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/BEGIN.7 postgresql-13-13.14/doc/src/sgml/man7/BEGIN.7 --- postgresql-13-13.13/doc/src/sgml/man7/BEGIN.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/BEGIN.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: BEGIN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "BEGIN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "BEGIN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CALL.7 postgresql-13-13.14/doc/src/sgml/man7/CALL.7 --- postgresql-13-13.13/doc/src/sgml/man7/CALL.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CALL.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CALL .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CALL" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CALL" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CHECKPOINT.7 postgresql-13-13.14/doc/src/sgml/man7/CHECKPOINT.7 --- postgresql-13-13.13/doc/src/sgml/man7/CHECKPOINT.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CHECKPOINT.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CHECKPOINT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CHECKPOINT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CHECKPOINT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CLOSE.7 postgresql-13-13.14/doc/src/sgml/man7/CLOSE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CLOSE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CLOSE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CLOSE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CLOSE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CLOSE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CLUSTER.7 postgresql-13-13.14/doc/src/sgml/man7/CLUSTER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CLUSTER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CLUSTER.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CLUSTER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CLUSTER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CLUSTER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/COMMENT.7 postgresql-13-13.14/doc/src/sgml/man7/COMMENT.7 --- postgresql-13-13.13/doc/src/sgml/man7/COMMENT.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/COMMENT.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: COMMENT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "COMMENT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "COMMENT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/COMMIT.7 postgresql-13-13.14/doc/src/sgml/man7/COMMIT.7 --- postgresql-13-13.13/doc/src/sgml/man7/COMMIT.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/COMMIT.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: COMMIT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "COMMIT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "COMMIT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/COMMIT_PREPARED.7 postgresql-13-13.14/doc/src/sgml/man7/COMMIT_PREPARED.7 --- postgresql-13-13.13/doc/src/sgml/man7/COMMIT_PREPARED.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/COMMIT_PREPARED.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: COMMIT PREPARED .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "COMMIT PREPARED" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "COMMIT PREPARED" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/COPY.7 postgresql-13-13.14/doc/src/sgml/man7/COPY.7 --- postgresql-13-13.13/doc/src/sgml/man7/COPY.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/COPY.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: COPY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "COPY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "COPY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -123,7 +123,9 @@ \fBUPDATE\fR and \fBDELETE\fR -queries a RETURNING clause must be provided, and the target relation must not have a conditional rule, nor an +queries a +RETURNING +clause must be provided, and the target relation must not have a conditional rule, nor an ALSO rule, nor an INSTEAD diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_ACCESS_METHOD.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE ACCESS METHOD .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE ACCESS METHOD" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE ACCESS METHOD" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_AGGREGATE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_AGGREGATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_AGGREGATE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_AGGREGATE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE AGGREGATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE AGGREGATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE AGGREGATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_CAST.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_CAST.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_CAST.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_CAST.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE CAST .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE CAST" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE CAST" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_COLLATION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_COLLATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_COLLATION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_COLLATION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE COLLATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE COLLATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE COLLATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_CONVERSION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_CONVERSION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_CONVERSION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_CONVERSION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE CONVERSION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE CONVERSION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE CONVERSION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_DATABASE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_DATABASE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_DATABASE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_DATABASE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE DATABASE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE DATABASE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE DATABASE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_DOMAIN.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_DOMAIN.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_DOMAIN.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_DOMAIN.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE DOMAIN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE DOMAIN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE DOMAIN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_EVENT_TRIGGER.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE EVENT TRIGGER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE EVENT TRIGGER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE EVENT TRIGGER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_EXTENSION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_EXTENSION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_EXTENSION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_EXTENSION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE EXTENSION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE EXTENSION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE EXTENSION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_FOREIGN_DATA_WRAPPER.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE FOREIGN DATA WRAPPER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE FOREIGN DATA WRAPPER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_FOREIGN_TABLE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE FOREIGN TABLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE FOREIGN TABLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE FOREIGN TABLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_FUNCTION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_FUNCTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_FUNCTION.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_FUNCTION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE FUNCTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE FUNCTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE FUNCTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_GROUP.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_GROUP.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_GROUP.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_GROUP.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE GROUP .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE GROUP" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE GROUP" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_INDEX.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_INDEX.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_INDEX.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_INDEX.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE INDEX .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE INDEX" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE INDEX" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_LANGUAGE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_LANGUAGE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_LANGUAGE.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_LANGUAGE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE LANGUAGE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE LANGUAGE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE LANGUAGE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_MATERIALIZED_VIEW.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE MATERIALIZED VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE MATERIALIZED VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_OPERATOR.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_OPERATOR.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_OPERATOR.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_OPERATOR.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE OPERATOR .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE OPERATOR" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE OPERATOR" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_OPERATOR_CLASS.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE OPERATOR CLASS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE OPERATOR CLASS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE OPERATOR CLASS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 2023-11-06 22:31:01.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_OPERATOR_FAMILY.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE OPERATOR FAMILY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE OPERATOR FAMILY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_POLICY.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_POLICY.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_POLICY.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_POLICY.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE POLICY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE POLICY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE POLICY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_PROCEDURE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_PROCEDURE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_PROCEDURE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_PROCEDURE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE PROCEDURE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE PROCEDURE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE PROCEDURE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_PUBLICATION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_PUBLICATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_PUBLICATION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_PUBLICATION.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE PUBLICATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE PUBLICATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE PUBLICATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_ROLE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_ROLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_ROLE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_ROLE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE ROLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE ROLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE ROLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_RULE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_RULE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_RULE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_RULE.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE RULE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE RULE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE RULE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_SCHEMA.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_SCHEMA.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_SCHEMA.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_SCHEMA.7 2024-02-05 22:04:40.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE SCHEMA .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE SCHEMA" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE SCHEMA" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_SEQUENCE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_SEQUENCE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_SEQUENCE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_SEQUENCE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE SEQUENCE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE SEQUENCE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE SEQUENCE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_SERVER.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_SERVER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_SERVER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_SERVER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE SERVER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE SERVER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE SERVER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_STATISTICS.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_STATISTICS.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_STATISTICS.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_STATISTICS.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE STATISTICS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE STATISTICS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE STATISTICS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_SUBSCRIPTION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE SUBSCRIPTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE SUBSCRIPTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE SUBSCRIPTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TABLE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TABLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TABLE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TABLE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TABLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TABLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TABLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -699,7 +699,9 @@ \fIrefcolumn\fR list is omitted, the primary key of the \fIreftable\fR -is used\&. The referenced columns must be the columns of a non\-deferrable unique or primary key constraint in the referenced table\&. The user must have +is used\&. Otherwise, the +\fIrefcolumn\fR +list must refer to the columns of a non\-deferrable unique or primary key constraint or be the columns of a non\-partial unique index\&. The user must have REFERENCES permission on the referenced table (either the whole table, or the specific referenced columns)\&. The addition of a foreign key constraint requires a SHARE ROW EXCLUSIVE @@ -1612,6 +1614,11 @@ constraint type is a PostgreSQL extension\&. +.SS "Foreign Key Constraints" +.PP +It is a +PostgreSQL +extension that a foreign key constraint may reference columns of a unique index instead of columns of a primary key or unique constraint\&. .SS "NULL \(lqConstraint\(rq" .PP The diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TABLESPACE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TABLESPACE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TABLESPACE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TABLESPACE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TABLESPACE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TABLESPACE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TABLESPACE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TABLE_AS.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TABLE_AS.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TABLE_AS.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TABLE_AS.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TABLE AS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TABLE AS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TABLE AS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_CONFIGURATION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TEXT SEARCH CONFIGURATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TEXT SEARCH CONFIGURATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_DICTIONARY.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TEXT SEARCH DICTIONARY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TEXT SEARCH DICTIONARY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_PARSER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TEXT SEARCH PARSER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TEXT SEARCH PARSER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TEXT_SEARCH_TEMPLATE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TEXT SEARCH TEMPLATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TEXT SEARCH TEMPLATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TRANSFORM.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TRANSFORM.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TRANSFORM.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TRANSFORM.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TRANSFORM .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TRANSFORM" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TRANSFORM" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TRIGGER.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TRIGGER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TRIGGER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TRIGGER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TRIGGER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TRIGGER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TRIGGER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_TYPE.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_TYPE.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_TYPE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_TYPE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE TYPE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE TYPE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE TYPE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_USER.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_USER.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_USER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_USER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE USER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE USER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE USER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_USER_MAPPING.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_USER_MAPPING.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_USER_MAPPING.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_USER_MAPPING.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE USER MAPPING .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE USER MAPPING" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE USER MAPPING" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/CREATE_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/CREATE_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/CREATE_VIEW.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/CREATE_VIEW.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: CREATE VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "CREATE VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "CREATE VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DEALLOCATE.7 postgresql-13-13.14/doc/src/sgml/man7/DEALLOCATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DEALLOCATE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DEALLOCATE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DEALLOCATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DEALLOCATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DEALLOCATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DECLARE.7 postgresql-13-13.14/doc/src/sgml/man7/DECLARE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DECLARE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DECLARE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DECLARE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DECLARE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DECLARE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DELETE.7 postgresql-13-13.14/doc/src/sgml/man7/DELETE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DELETE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DELETE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DELETE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DELETE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DELETE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DISCARD.7 postgresql-13-13.14/doc/src/sgml/man7/DISCARD.7 --- postgresql-13-13.13/doc/src/sgml/man7/DISCARD.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DISCARD.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DISCARD .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DISCARD" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DISCARD" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DO.7 postgresql-13-13.14/doc/src/sgml/man7/DO.7 --- postgresql-13-13.13/doc/src/sgml/man7/DO.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DO.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DO .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DO" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DO" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_ACCESS_METHOD.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP ACCESS METHOD .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP ACCESS METHOD" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP ACCESS METHOD" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_AGGREGATE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_AGGREGATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_AGGREGATE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_AGGREGATE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP AGGREGATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP AGGREGATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP AGGREGATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_CAST.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_CAST.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_CAST.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_CAST.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP CAST .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP CAST" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP CAST" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_COLLATION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_COLLATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_COLLATION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_COLLATION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP COLLATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP COLLATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP COLLATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_CONVERSION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_CONVERSION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_CONVERSION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_CONVERSION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP CONVERSION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP CONVERSION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP CONVERSION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_DATABASE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_DATABASE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_DATABASE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_DATABASE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP DATABASE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP DATABASE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP DATABASE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_DOMAIN.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_DOMAIN.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_DOMAIN.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_DOMAIN.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP DOMAIN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP DOMAIN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP DOMAIN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_EVENT_TRIGGER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP EVENT TRIGGER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP EVENT TRIGGER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP EVENT TRIGGER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_EXTENSION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_EXTENSION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_EXTENSION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_EXTENSION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP EXTENSION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP EXTENSION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP EXTENSION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_FOREIGN_DATA_WRAPPER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP FOREIGN DATA WRAPPER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP FOREIGN DATA WRAPPER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP FOREIGN DATA WRAPPER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_FOREIGN_TABLE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP FOREIGN TABLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP FOREIGN TABLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP FOREIGN TABLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_FUNCTION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_FUNCTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_FUNCTION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_FUNCTION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP FUNCTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP FUNCTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP FUNCTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_GROUP.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_GROUP.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_GROUP.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_GROUP.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP GROUP .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP GROUP" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP GROUP" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_INDEX.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_INDEX.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_INDEX.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_INDEX.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP INDEX .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP INDEX" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP INDEX" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_LANGUAGE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_LANGUAGE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_LANGUAGE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_LANGUAGE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP LANGUAGE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP LANGUAGE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP LANGUAGE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_MATERIALIZED_VIEW.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP MATERIALIZED VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP MATERIALIZED VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_OPERATOR.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_OPERATOR.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_OPERATOR.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_OPERATOR.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP OPERATOR .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP OPERATOR" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP OPERATOR" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_OPERATOR_CLASS.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP OPERATOR CLASS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP OPERATOR CLASS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP OPERATOR CLASS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_OPERATOR_FAMILY.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP OPERATOR FAMILY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP OPERATOR FAMILY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP OPERATOR FAMILY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_OWNED.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_OWNED.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_OWNED.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_OWNED.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP OWNED .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP OWNED" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP OWNED" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_POLICY.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_POLICY.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_POLICY.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_POLICY.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP POLICY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP POLICY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP POLICY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_PROCEDURE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_PROCEDURE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_PROCEDURE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_PROCEDURE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP PROCEDURE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP PROCEDURE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP PROCEDURE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_PUBLICATION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_PUBLICATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_PUBLICATION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_PUBLICATION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP PUBLICATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP PUBLICATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP PUBLICATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_ROLE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_ROLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_ROLE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_ROLE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP ROLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP ROLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP ROLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_ROUTINE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_ROUTINE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_ROUTINE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_ROUTINE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP ROUTINE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP ROUTINE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP ROUTINE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_RULE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_RULE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_RULE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_RULE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP RULE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP RULE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP RULE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_SCHEMA.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_SCHEMA.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_SCHEMA.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_SCHEMA.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP SCHEMA .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP SCHEMA" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP SCHEMA" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_SEQUENCE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_SEQUENCE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_SEQUENCE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_SEQUENCE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP SEQUENCE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP SEQUENCE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP SEQUENCE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_SERVER.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_SERVER.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_SERVER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_SERVER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP SERVER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP SERVER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP SERVER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_STATISTICS.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_STATISTICS.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_STATISTICS.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_STATISTICS.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP STATISTICS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP STATISTICS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP STATISTICS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_SUBSCRIPTION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP SUBSCRIPTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP SUBSCRIPTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP SUBSCRIPTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TABLE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TABLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TABLE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TABLE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TABLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TABLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TABLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TABLESPACE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TABLESPACE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TABLESPACE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TABLESPACE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TABLESPACE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TABLESPACE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TABLESPACE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_CONFIGURATION.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TEXT SEARCH CONFIGURATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TEXT SEARCH CONFIGURATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TEXT SEARCH CONFIGURATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_DICTIONARY.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TEXT SEARCH DICTIONARY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TEXT SEARCH DICTIONARY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TEXT SEARCH DICTIONARY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_PARSER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TEXT SEARCH PARSER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TEXT SEARCH PARSER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TEXT SEARCH PARSER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TEXT_SEARCH_TEMPLATE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TEXT SEARCH TEMPLATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TEXT SEARCH TEMPLATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TEXT SEARCH TEMPLATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TRANSFORM.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TRANSFORM.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TRANSFORM.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TRANSFORM.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TRANSFORM .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TRANSFORM" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TRANSFORM" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TRIGGER.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TRIGGER.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TRIGGER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TRIGGER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TRIGGER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TRIGGER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TRIGGER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_TYPE.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_TYPE.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_TYPE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_TYPE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP TYPE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP TYPE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP TYPE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_USER.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_USER.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_USER.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_USER.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP USER .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP USER" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP USER" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_USER_MAPPING.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_USER_MAPPING.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_USER_MAPPING.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_USER_MAPPING.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP USER MAPPING .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP USER MAPPING" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP USER MAPPING" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/DROP_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/DROP_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/DROP_VIEW.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/DROP_VIEW.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: DROP VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "DROP VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "DROP VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/END.7 postgresql-13-13.14/doc/src/sgml/man7/END.7 --- postgresql-13-13.13/doc/src/sgml/man7/END.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/END.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: END .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "END" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "END" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/EXECUTE.7 postgresql-13-13.14/doc/src/sgml/man7/EXECUTE.7 --- postgresql-13-13.13/doc/src/sgml/man7/EXECUTE.7 2023-11-06 22:31:02.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/EXECUTE.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: EXECUTE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "EXECUTE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "EXECUTE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/EXPLAIN.7 postgresql-13-13.14/doc/src/sgml/man7/EXPLAIN.7 --- postgresql-13-13.13/doc/src/sgml/man7/EXPLAIN.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/EXPLAIN.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: EXPLAIN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "EXPLAIN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "EXPLAIN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/FETCH.7 postgresql-13-13.14/doc/src/sgml/man7/FETCH.7 --- postgresql-13-13.13/doc/src/sgml/man7/FETCH.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/FETCH.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: FETCH .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "FETCH" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "FETCH" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/GRANT.7 postgresql-13-13.14/doc/src/sgml/man7/GRANT.7 --- postgresql-13-13.13/doc/src/sgml/man7/GRANT.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/GRANT.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: GRANT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "GRANT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "GRANT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 postgresql-13-13.14/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 --- postgresql-13-13.13/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/IMPORT_FOREIGN_SCHEMA.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: IMPORT FOREIGN SCHEMA .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "IMPORT FOREIGN SCHEMA" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "IMPORT FOREIGN SCHEMA" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/INSERT.7 postgresql-13-13.14/doc/src/sgml/man7/INSERT.7 --- postgresql-13-13.13/doc/src/sgml/man7/INSERT.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/INSERT.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: INSERT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "INSERT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "INSERT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/LISTEN.7 postgresql-13-13.14/doc/src/sgml/man7/LISTEN.7 --- postgresql-13-13.13/doc/src/sgml/man7/LISTEN.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/LISTEN.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: LISTEN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "LISTEN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "LISTEN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/LOAD.7 postgresql-13-13.14/doc/src/sgml/man7/LOAD.7 --- postgresql-13-13.13/doc/src/sgml/man7/LOAD.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/LOAD.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: LOAD .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "LOAD" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "LOAD" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/LOCK.7 postgresql-13-13.14/doc/src/sgml/man7/LOCK.7 --- postgresql-13-13.13/doc/src/sgml/man7/LOCK.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/LOCK.7 2024-02-05 22:04:41.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: LOCK .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "LOCK" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "LOCK" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/MOVE.7 postgresql-13-13.14/doc/src/sgml/man7/MOVE.7 --- postgresql-13-13.13/doc/src/sgml/man7/MOVE.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/MOVE.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: MOVE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "MOVE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "MOVE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/NOTIFY.7 postgresql-13-13.14/doc/src/sgml/man7/NOTIFY.7 --- postgresql-13-13.13/doc/src/sgml/man7/NOTIFY.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/NOTIFY.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: NOTIFY .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "NOTIFY" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "NOTIFY" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/PREPARE.7 postgresql-13-13.14/doc/src/sgml/man7/PREPARE.7 --- postgresql-13-13.13/doc/src/sgml/man7/PREPARE.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/PREPARE.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: PREPARE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PREPARE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PREPARE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/PREPARE_TRANSACTION.7 postgresql-13-13.14/doc/src/sgml/man7/PREPARE_TRANSACTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/PREPARE_TRANSACTION.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/PREPARE_TRANSACTION.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: PREPARE TRANSACTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "PREPARE TRANSACTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "PREPARE TRANSACTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/REASSIGN_OWNED.7 postgresql-13-13.14/doc/src/sgml/man7/REASSIGN_OWNED.7 --- postgresql-13-13.13/doc/src/sgml/man7/REASSIGN_OWNED.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/REASSIGN_OWNED.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: REASSIGN OWNED .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "REASSIGN OWNED" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "REASSIGN OWNED" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 postgresql-13-13.14/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 --- postgresql-13-13.13/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/REFRESH_MATERIALIZED_VIEW.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: REFRESH MATERIALIZED VIEW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "REFRESH MATERIALIZED VIEW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "REFRESH MATERIALIZED VIEW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/REINDEX.7 postgresql-13-13.14/doc/src/sgml/man7/REINDEX.7 --- postgresql-13-13.13/doc/src/sgml/man7/REINDEX.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/REINDEX.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: REINDEX .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "REINDEX" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "REINDEX" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 postgresql-13-13.14/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 --- postgresql-13-13.13/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/RELEASE_SAVEPOINT.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: RELEASE SAVEPOINT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "RELEASE SAVEPOINT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "RELEASE SAVEPOINT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/RESET.7 postgresql-13-13.14/doc/src/sgml/man7/RESET.7 --- postgresql-13-13.13/doc/src/sgml/man7/RESET.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/RESET.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: RESET .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "RESET" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "RESET" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/REVOKE.7 postgresql-13-13.14/doc/src/sgml/man7/REVOKE.7 --- postgresql-13-13.13/doc/src/sgml/man7/REVOKE.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/REVOKE.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: REVOKE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "REVOKE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "REVOKE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ROLLBACK.7 postgresql-13-13.14/doc/src/sgml/man7/ROLLBACK.7 --- postgresql-13-13.13/doc/src/sgml/man7/ROLLBACK.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ROLLBACK.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ROLLBACK .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ROLLBACK" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ROLLBACK" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ROLLBACK_PREPARED.7 postgresql-13-13.14/doc/src/sgml/man7/ROLLBACK_PREPARED.7 --- postgresql-13-13.13/doc/src/sgml/man7/ROLLBACK_PREPARED.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ROLLBACK_PREPARED.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ROLLBACK PREPARED .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ROLLBACK PREPARED" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ROLLBACK PREPARED" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 postgresql-13-13.14/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 --- postgresql-13-13.13/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/ROLLBACK_TO_SAVEPOINT.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: ROLLBACK TO SAVEPOINT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "ROLLBACK TO SAVEPOINT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "ROLLBACK TO SAVEPOINT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SAVEPOINT.7 postgresql-13-13.14/doc/src/sgml/man7/SAVEPOINT.7 --- postgresql-13-13.13/doc/src/sgml/man7/SAVEPOINT.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SAVEPOINT.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SAVEPOINT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SAVEPOINT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SAVEPOINT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SECURITY_LABEL.7 postgresql-13-13.14/doc/src/sgml/man7/SECURITY_LABEL.7 --- postgresql-13-13.13/doc/src/sgml/man7/SECURITY_LABEL.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SECURITY_LABEL.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SECURITY LABEL .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SECURITY LABEL" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SECURITY LABEL" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SELECT.7 postgresql-13-13.14/doc/src/sgml/man7/SELECT.7 --- postgresql-13-13.13/doc/src/sgml/man7/SELECT.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SELECT.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SELECT .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SELECT" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SELECT" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- @@ -2180,8 +2180,7 @@ ) SELECT * FROM t UNION ALL -SELECT * FROM t - +SELECT * FROM t; x \-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\-\- 0\&.534150459803641 diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SELECT_INTO.7 postgresql-13-13.14/doc/src/sgml/man7/SELECT_INTO.7 --- postgresql-13-13.13/doc/src/sgml/man7/SELECT_INTO.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SELECT_INTO.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SELECT INTO .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SELECT INTO" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SELECT INTO" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SET.7 postgresql-13-13.14/doc/src/sgml/man7/SET.7 --- postgresql-13-13.13/doc/src/sgml/man7/SET.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SET.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SET .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SET" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SET" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SET_CONSTRAINTS.7 postgresql-13-13.14/doc/src/sgml/man7/SET_CONSTRAINTS.7 --- postgresql-13-13.13/doc/src/sgml/man7/SET_CONSTRAINTS.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SET_CONSTRAINTS.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SET CONSTRAINTS .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SET CONSTRAINTS" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SET CONSTRAINTS" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SET_ROLE.7 postgresql-13-13.14/doc/src/sgml/man7/SET_ROLE.7 --- postgresql-13-13.13/doc/src/sgml/man7/SET_ROLE.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SET_ROLE.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SET ROLE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SET ROLE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SET ROLE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 postgresql-13-13.14/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 --- postgresql-13-13.13/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SET_SESSION_AUTHORIZATION.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SET SESSION AUTHORIZATION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SET SESSION AUTHORIZATION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SET SESSION AUTHORIZATION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SET_TRANSACTION.7 postgresql-13-13.14/doc/src/sgml/man7/SET_TRANSACTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/SET_TRANSACTION.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SET_TRANSACTION.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SET TRANSACTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SET TRANSACTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SET TRANSACTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/SHOW.7 postgresql-13-13.14/doc/src/sgml/man7/SHOW.7 --- postgresql-13-13.13/doc/src/sgml/man7/SHOW.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/SHOW.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: SHOW .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "SHOW" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "SHOW" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/START_TRANSACTION.7 postgresql-13-13.14/doc/src/sgml/man7/START_TRANSACTION.7 --- postgresql-13-13.13/doc/src/sgml/man7/START_TRANSACTION.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/START_TRANSACTION.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: START TRANSACTION .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "START TRANSACTION" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "START TRANSACTION" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/TRUNCATE.7 postgresql-13-13.14/doc/src/sgml/man7/TRUNCATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/TRUNCATE.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/TRUNCATE.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: TRUNCATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "TRUNCATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "TRUNCATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/UNLISTEN.7 postgresql-13-13.14/doc/src/sgml/man7/UNLISTEN.7 --- postgresql-13-13.13/doc/src/sgml/man7/UNLISTEN.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/UNLISTEN.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: UNLISTEN .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "UNLISTEN" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "UNLISTEN" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/UPDATE.7 postgresql-13-13.14/doc/src/sgml/man7/UPDATE.7 --- postgresql-13-13.13/doc/src/sgml/man7/UPDATE.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/UPDATE.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: UPDATE .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "UPDATE" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "UPDATE" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/VACUUM.7 postgresql-13-13.14/doc/src/sgml/man7/VACUUM.7 --- postgresql-13-13.13/doc/src/sgml/man7/VACUUM.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/VACUUM.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: VACUUM .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "VACUUM" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "VACUUM" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/man7/VALUES.7 postgresql-13-13.14/doc/src/sgml/man7/VALUES.7 --- postgresql-13-13.13/doc/src/sgml/man7/VALUES.7 2023-11-06 22:31:03.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/man7/VALUES.7 2024-02-05 22:04:42.000000000 +0000 @@ -2,12 +2,12 @@ .\" Title: VALUES .\" Author: The PostgreSQL Global Development Group .\" Generator: DocBook XSL Stylesheets vsnapshot -.\" Date: 2023 -.\" Manual: PostgreSQL 13.13 Documentation -.\" Source: PostgreSQL 13.13 +.\" Date: 2024 +.\" Manual: PostgreSQL 13.14 Documentation +.\" Source: PostgreSQL 13.14 .\" Language: English .\" -.TH "VALUES" "7" "2023" "PostgreSQL 13.13" "PostgreSQL 13.13 Documentation" +.TH "VALUES" "7" "2024" "PostgreSQL 13.14" "PostgreSQL 13.14 Documentation" .\" ----------------------------------------------------------------- .\" * Define some portability stuff .\" ----------------------------------------------------------------- diff -Nru postgresql-13-13.13/doc/src/sgml/plpython.sgml postgresql-13-13.14/doc/src/sgml/plpython.sgml --- postgresql-13-13.13/doc/src/sgml/plpython.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/plpython.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1323,7 +1323,7 @@ plpy.execute(plan, [result]) $$ LANGUAGE plpythonu; - Note that the use of try/catch is still + Note that the use of try/except is still required. Otherwise the exception would propagate to the top of the Python stack and would cause the whole function to abort with a PostgreSQL error, so that the diff -Nru postgresql-13-13.13/doc/src/sgml/protocol.sgml postgresql-13-13.14/doc/src/sgml/protocol.sgml --- postgresql-13-13.13/doc/src/sgml/protocol.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/protocol.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -2518,7 +2518,10 @@ option_name - The name of an option passed to the slot's logical decoding plugin. + The name of an option passed to the slot's logical decoding output + plugin. See for + options that are accepted by the standard (pgoutput) + plugin. @@ -2863,12 +2866,18 @@ the physical streaming replication protocol. + + PostgreSQL logical decoding supports output + plugins. pgoutput is the standard one used for + the built-in logical replication. + + Logical Streaming Replication Parameters - The logical replication START_REPLICATION command - accepts following parameters: + Using the START_REPLICATION command, + pgoutput accepts the following options: @@ -2878,7 +2887,7 @@ Protocol version. Currently only version 1 is - supported. + supported. A valid version is required. @@ -2892,6 +2901,7 @@ Comma separated list of publication names for which to subscribe (receive changes). The individual publication names are treated as standard objects names and can be quoted the same as needed. + At least one publication name is required. diff -Nru postgresql-13-13.13/doc/src/sgml/ref/alter_event_trigger.sgml postgresql-13-13.14/doc/src/sgml/ref/alter_event_trigger.sgml --- postgresql-13-13.13/doc/src/sgml/ref/alter_event_trigger.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/ref/alter_event_trigger.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -73,7 +73,7 @@ - DISABLE/ENABLE [ REPLICA | ALWAYS ] TRIGGER + DISABLE/ENABLE [ REPLICA | ALWAYS ] These forms configure the firing of event triggers. A disabled trigger diff -Nru postgresql-13-13.13/doc/src/sgml/ref/alter_foreign_data_wrapper.sgml postgresql-13-13.14/doc/src/sgml/ref/alter_foreign_data_wrapper.sgml --- postgresql-13-13.13/doc/src/sgml/ref/alter_foreign_data_wrapper.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/ref/alter_foreign_data_wrapper.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -153,7 +153,7 @@ Change a foreign-data wrapper dbi, add option foo, drop bar: -ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP 'bar'); +ALTER FOREIGN DATA WRAPPER dbi OPTIONS (ADD foo '1', DROP bar); diff -Nru postgresql-13-13.13/doc/src/sgml/ref/copy.sgml postgresql-13-13.14/doc/src/sgml/ref/copy.sgml --- postgresql-13-13.13/doc/src/sgml/ref/copy.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/ref/copy.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -119,10 +119,10 @@ For INSERT, UPDATE and - DELETE queries a RETURNING clause must be provided, - and the target relation must not have a conditional rule, nor - an ALSO rule, nor an INSTEAD rule - that expands to multiple statements. + DELETE queries a RETURNING clause + must be provided, and the target relation must not have a conditional + rule, nor an ALSO rule, nor an + INSTEAD rule that expands to multiple statements. diff -Nru postgresql-13-13.13/doc/src/sgml/ref/create_table.sgml postgresql-13-13.14/doc/src/sgml/ref/create_table.sgml --- postgresql-13-13.13/doc/src/sgml/ref/create_table.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/ref/create_table.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1049,10 +1049,11 @@ column(s) of some row of the referenced table. If the refcolumn list is omitted, the primary key of the reftable - is used. The referenced columns must be the columns of a non-deferrable - unique or primary key constraint in the referenced table. The user - must have REFERENCES permission on the referenced table - (either the whole table, or the specific referenced columns). The + is used. Otherwise, the refcolumn + list must refer to the columns of a non-deferrable unique or primary key + constraint or be the columns of a non-partial unique index. The user + must have REFERENCES permission on the referenced + table (either the whole table, or the specific referenced columns). The addition of a foreign key constraint requires a SHARE ROW EXCLUSIVE lock on the referenced table. Note that foreign key constraints cannot be defined between temporary @@ -2177,6 +2178,16 @@ + + Foreign Key Constraints + + + It is a PostgreSQL extension that a + foreign key constraint may reference columns of a unique index instead of + columns of a primary key or unique constraint. + + + <literal>NULL</literal> <quote>Constraint</quote> diff -Nru postgresql-13-13.13/doc/src/sgml/ref/select.sgml postgresql-13-13.14/doc/src/sgml/ref/select.sgml --- postgresql-13-13.13/doc/src/sgml/ref/select.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/ref/select.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1857,8 +1857,7 @@ ) SELECT * FROM t UNION ALL -SELECT * FROM t - +SELECT * FROM t; x -------------------- 0.534150459803641 diff -Nru postgresql-13-13.13/doc/src/sgml/release-13.sgml postgresql-13-13.14/doc/src/sgml/release-13.sgml --- postgresql-13-13.13/doc/src/sgml/release-13.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/release-13.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1,6 +1,949 @@ + + Release 13.14 + + + Release date: + 2024-02-08 + + + + This release contains a variety of fixes from 13.13. + For information about new features in major release 13, see + . + + + + Migration to Version 13.14 + + + A dump/restore is not required for those running 13.X. + + + + However, one bug was fixed that could have resulted in corruption of + GIN indexes during concurrent updates. If you suspect such + corruption, reindex affected indexes after installing this update. + + + + Also, if you are upgrading from a version earlier than 13.13, + see . + + + + + Changes + + + + + + + Tighten security restrictions within REFRESH MATERIALIZED + VIEW CONCURRENTLY (Heikki Linnakangas) + + + + One step of a concurrent refresh command was run under weak security + restrictions. If a materialized view's owner could persuade a + superuser or other high-privileged user to perform a concurrent + refresh on that view, the view's owner could control code executed + with the privileges of the user running REFRESH. + Fix things so that all user-determined code is run as the view's + owner, as expected. + + + + The only known exploit for this error does not work + in PostgreSQL 16.0 and later, so it may + be that v16 is not vulnerable in practice. + + + + The PostgreSQL Project thanks Pedro + Gallegos for reporting this problem. + (CVE-2024-0985) + + + + + + + Fix memory leak when performing JIT inlining (Andres Freund, + Daniel Gustafsson) + + + + There have been multiple reports of backend processes suffering + out-of-memory conditions after sufficiently many JIT compilations. + This fix should resolve that. + + + + + + + When dequeueing from an LWLock, avoid needing to search the list of + waiting processes (Andres Freund) + + + + This fixes O(N^2) behavior when the list of waiters is long. In + some use-cases this results in substantial throughput improvements. + + + + + + + Avoid generating incorrect partitioned-join plans (Richard Guo) + + + + Some uncommon situations involving lateral references could create + incorrect plans. Affected queries could produce wrong answers, or + odd failures such as variable not found in subplan target + list, or executor crashes. + + + + + + + Fix incorrect wrapping of subquery output expressions in + PlaceHolderVars (Tom Lane) + + + + This fixes incorrect results when a subquery is underneath an outer + join and has an output column that laterally references something + outside the outer join's scope. The output column might not appear + as NULL when it should do so due to the action of the outer join. + + + + + + + Avoid requesting an oversize shared-memory area in parallel hash + join (Thomas Munro, Andrei Lepikhov, Alexander Korotkov) + + + + The limiting value was too large, allowing invalid DSA memory + alloc request size errors to occur with sufficiently large + expected hash table sizes. + + + + + + + Avoid assertion failures in heap_update() + and heap_delete() when a tuple to be updated by + a foreign-key enforcement trigger fails the extra visibility + crosscheck (Alexander Lakhin) + + + + This error had no impact in non-assert builds. + + + + + + + Fix possible failure during ALTER TABLE ADD + COLUMN on a complex inheritance tree (Tender Wang) + + + + If a grandchild table would inherit the new column via multiple + intermediate parents, the command failed with tuple already + updated by self. + + + + + + + Fix problems with duplicate token names in ALTER TEXT + SEARCH CONFIGURATION ... MAPPING commands (Tender Wang, + Michael Paquier) + + + + + + + Properly lock the associated table during DROP + STATISTICS (Tomas Vondra) + + + + Failure to acquire the lock could result in tuple + concurrently deleted errors if the DROP + executes concurrently with ANALYZE. + + + + + + + Fix function volatility checking for GENERATED + and DEFAULT expressions (Tom Lane) + + + + These places could fail to detect insertion of a volatile function + default-argument expression, or decide that a polymorphic function + is volatile although it is actually immutable on the datatype of + interest. This could lead to improperly rejecting or accepting + a GENERATED clause, or to mistakenly applying the + constant-default-value optimization in ALTER TABLE ADD + COLUMN. + + + + + + + Detect that a new catalog cache entry became stale while detoasting + its fields (Tom Lane) + + + + We expand any out-of-line fields in a catalog tuple before inserting + it into the catalog caches. That involves database access which + might cause invalidation of catalog cache entries — but the + new entry isn't in the cache yet, so we would miss noticing that it + should get invalidated. The result is a race condition in which an + already-stale cache entry could get made, and then persist + indefinitely. This would lead to hard-to-predict misbehavior. + Fix by rechecking the tuple's visibility after detoasting. + + + + + + + Fix edge-case integer overflow detection bug on some platforms (Dean + Rasheed) + + + + Computing 0 - INT64_MIN should result in an + overflow error, and did on most platforms. However, platforms with + neither integer overflow builtins nor 128-bit integers would fail to + spot the overflow, instead returning INT64_MIN. + + + + + + + Detect Julian-date overflow when adding or subtracting + an interval to/from a timestamp (Tom Lane) + + + + Some cases that should cause an out-of-range error produced an + incorrect result instead. + + + + + + + Add more checks for overflow in interval_mul() + and interval_div() (Dean Rasheed) + + + + Some cases that should cause an out-of-range error produced an + incorrect result instead. + + + + + + + Make the pg_file_settings view check + validity of unapplied values for settings + with backend + or superuser-backend context (Tom Lane) + + + + Invalid values were not noted in the view as intended. This escaped + detection because there are very few settings in these groups. + + + + + + + Match collation too when matching an existing index to a new + partitioned index (Peter Eisentraut) + + + + Previously we could accept an index that has a different collation + from the corresponding element of the partition key, possibly + leading to misbehavior. + + + + + + + Fix insufficient locking when cleaning up an incomplete split of + a GIN index's internal page (Fei Changhong, Heikki Linnakangas) + + + + The code tried to do this with shared rather than exclusive lock on + the buffer. This could lead to index corruption if two processes + attempted the cleanup concurrently. + + + + + + + Avoid premature release of buffer pin in GIN index insertion + (Tom Lane) + + + + If an index root page split occurs concurrently with our own + insertion, the code could fail with buffer NNNN is not owned + by resource owner. + + + + + + + Avoid failure with partitioned SP-GiST indexes (Tom Lane) + + + + Trying to use an index of this kind could lead to No such + file or directory errors. + + + + + + + Fix ownership change reporting for large objects (Tom Lane) + + + + A no-op ALTER LARGE OBJECT OWNER command (that + is, one selecting the existing owner) passed the wrong class ID to + the PostAlterHook, probably confusing any + extension using that hook. + + + + + + + Prevent standby servers from incorrectly processing dead index + tuples during subtransactions (Fei Changhong) + + + + The startedInRecovery flag was not + correctly set for a subtransaction. This affects only processing of + dead index tuples. It could allow a query in a subtransaction to + ignore index entries that it should return (if they are already dead + on the primary server, but not dead to the standby transaction), or + to prematurely mark index entries as dead that are not yet dead on + the primary. It is not clear that the latter case has any serious + consequences, but it's not the intended behavior. + + + + + + + Fix deadlock between a logical replication apply worker, its + tablesync worker, and a session process trying to alter the + subscription (Shlok Kyal) + + + + One edge of the deadlock loop did not involve a lock wait, so the + deadlock went undetected and would persist until manual + intervention. + + + + + + + Return the correct status code when a new client disconnects without + responding to the server's password challenge (Liu Lang, Tom Lane) + + + + In some cases we'd treat this as a loggable error, which was not the + intention and tends to create log spam, since common clients + like psql frequently do this. It may + also confuse extensions that + use ClientAuthentication_hook. + + + + + + + Fix incompatibility with OpenSSL 3.2 + (Tristan Partin, Bo Andreson) + + + + Use the BIO app_data field for our private storage, + instead of assuming it's okay to use the data field. + This mistake didn't cause problems before, but with 3.2 it leads + to crashes and complaints about double frees. + + + + + + + Be more wary about OpenSSL not + setting errno on error (Tom Lane) + + + + If errno isn't set, assume the cause of the + reported failure is read EOF. This fixes rare cases of strange + error reports like could not accept SSL connection: + Success. + + + + + + + Report ENOMEM errors from file-related system + calls as ERRCODE_OUT_OF_MEMORY, + not ERRCODE_INTERNAL_ERROR (Alexander Kuzmenkov) + + + + + + + Avoid race condition when libpq + initializes OpenSSL support concurrently in two different threads + (Willi Mann, Michael Paquier) + + + + + + + Fix timing-dependent failure in GSSAPI data transmission (Tom Lane) + + + + When using GSSAPI encryption in non-blocking + mode, libpq sometimes failed + with GSSAPI caller failed to retransmit all data needing to + be retried. + + + + + + + In pg_dump, don't dump RLS policies or + security labels for extension member objects (Tom Lane, Jacob + Champion) + + + + Previously, commands would be included in the dump to set these + properties, which is really incorrect since they should be + considered as internal affairs of the extension. Moreover, the + restoring user might not have adequate privilege to set them, and + indeed the dumping user might not have enough privilege to dump them + (since dumping RLS policies requires acquiring lock on their table). + + + + + + + In pg_dump, don't dump an extended + statistics object if its underlying table isn't being dumped + (Rian McGuire, Tom Lane) + + + + This conforms to the behavior for other dependent objects such as + indexes. + + + + + + + Fix crash in contrib/intarray if an array with + an element equal to INT_MAX is inserted into + a gist__int_ops index + (Alexander Lakhin, Tom Lane) + + + + + + + Report a better error + when contrib/pageinspect's + hash_bitmap_info() function is applied to a + partitioned hash index (Alexander Lakhin, Michael Paquier) + + + + + + + Report a better error + when contrib/pgstattuple's + pgstathashindex() function is applied to a + partitioned hash index (Alexander Lakhin) + + + + + + + On Windows, suppress autorun options when launching subprocesses + in pg_ctl + and pg_regress (Kyotaro Horiguchi) + + + + When launching a child process via cmd.exe, + pass the flag to prevent executing any autorun + commands specified in the registry. This avoids possibly-surprising + side effects. + + + + + + + Fix compilation failures with libxml2 + version 2.12.0 and later (Tom Lane) + + + + + + + Fix compilation failure of WAL_DEBUG code on + Windows (Bharath Rupireddy) + + + + + + + Suppress compiler warnings from Python's header files + (Peter Eisentraut, Tom Lane) + + + + Our preferred compiler options provoke warnings about constructs + appearing in recent versions of Python's header files. When using + gcc, we can suppress these warnings with + a pragma. + + + + + + + Avoid deprecation warning when compiling with LLVM 18 (Thomas Munro) + + + + + + + Update time zone data files to tzdata + release 2024a for DST law changes in Greenland, Kazakhstan, and + Palestine, plus corrections for the Antarctic stations Casey and + Vostok. Also historical corrections for Vietnam, Toronto, and + Miquelon. + + + + + + + + Release 13.13 @@ -1246,7 +2189,7 @@ - The PostgreSQL Project thanks Micah Gate, + The PostgreSQL Project thanks Micah Gates, Valerie Woolard, Tim Carey-Smith, and Christoph Berg for reporting this problem. (CVE-2023-39417) diff -Nru postgresql-13-13.13/doc/src/sgml/syntax.sgml postgresql-13-13.14/doc/src/sgml/syntax.sgml --- postgresql-13-13.13/doc/src/sgml/syntax.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/syntax.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -1022,6 +1022,18 @@ + COLLATE + left + collation selection + + + + AT + left + AT TIME ZONE + + + ^ left exponentiation diff -Nru postgresql-13-13.13/doc/src/sgml/wal.sgml postgresql-13-13.14/doc/src/sgml/wal.sgml --- postgresql-13-13.13/doc/src/sgml/wal.sgml 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/doc/src/sgml/wal.sgml 2024-02-05 21:47:02.000000000 +0000 @@ -85,7 +85,7 @@ On FreeBSD, IDE drives can be queried using - atacontrol and write caching turned off using + camcontrol identify and write caching turned off using hw.ata.wc=0 in /boot/loader.conf; SCSI drives can be queried using camcontrol identify, and the write cache both queried and changed using diff -Nru postgresql-13-13.13/src/backend/access/gin/ginbtree.c postgresql-13-13.14/src/backend/access/gin/ginbtree.c --- postgresql-13-13.13/src/backend/access/gin/ginbtree.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/gin/ginbtree.c 2024-02-05 21:47:02.000000000 +0000 @@ -28,6 +28,8 @@ Buffer childbuf, GinStatsData *buildStats); static void ginFinishSplit(GinBtree btree, GinBtreeStack *stack, bool freestack, GinStatsData *buildStats); +static void ginFinishOldSplit(GinBtree btree, GinBtreeStack *stack, + GinStatsData *buildStats, int access); /* * Lock buffer by needed method for search. @@ -109,7 +111,7 @@ * encounter on the way. */ if (!searchMode && GinPageIsIncompleteSplit(page)) - ginFinishSplit(btree, stack, false, NULL); + ginFinishOldSplit(btree, stack, NULL, access); /* * ok, page is correctly locked, we should check to move right .., @@ -130,7 +132,7 @@ TestForOldSnapshot(snapshot, btree->index, page); if (!searchMode && GinPageIsIncompleteSplit(page)) - ginFinishSplit(btree, stack, false, NULL); + ginFinishOldSplit(btree, stack, NULL, access); } if (GinPageIsLeaf(page)) /* we found, return locked page */ @@ -166,8 +168,11 @@ * Step right from current page. * * The next page is locked first, before releasing the current page. This is - * crucial to protect from concurrent page deletion (see comment in - * ginDeletePage). + * crucial to prevent concurrent VACUUM from deleting a page that we are about + * to step to. (The lock-coupling isn't strictly necessary when we are + * traversing the tree to find an insert location, because page deletion grabs + * a cleanup lock on the root to prevent any concurrent inserts. See Page + * deletion section in the README. But there's no harm in doing it always.) */ Buffer ginStepRight(Buffer buffer, Relation index, int lockmode) @@ -265,7 +270,7 @@ ptr->parent = root; ptr->off = InvalidOffsetNumber; - ginFinishSplit(btree, ptr, false, NULL); + ginFinishOldSplit(btree, ptr, NULL, GIN_EXCLUSIVE); } leftmostBlkno = btree->getLeftMostChild(btree, page); @@ -275,7 +280,11 @@ blkno = GinPageGetOpaque(page)->rightlink; if (blkno == InvalidBlockNumber) { - UnlockReleaseBuffer(buffer); + /* Link not present in this level */ + LockBuffer(buffer, GIN_UNLOCK); + /* Do not release pin on the root buffer */ + if (buffer != root->buffer) + ReleaseBuffer(buffer); break; } buffer = ginStepRight(buffer, btree->index, GIN_EXCLUSIVE); @@ -290,7 +299,7 @@ ptr->parent = root; ptr->off = InvalidOffsetNumber; - ginFinishSplit(btree, ptr, false, NULL); + ginFinishOldSplit(btree, ptr, NULL, GIN_EXCLUSIVE); } } @@ -672,15 +681,6 @@ bool done; bool first = true; - /* - * freestack == false when we encounter an incompletely split page during - * a scan, while freestack == true is used in the normal scenario that a - * split is finished right after the initial insert. - */ - if (!freestack) - elog(DEBUG1, "finishing incomplete split of block %u in gin index \"%s\"", - stack->blkno, RelationGetRelationName(btree->index)); - /* this loop crawls up the stack until the insertion is complete */ do { @@ -701,7 +701,7 @@ * would fail. */ if (GinPageIsIncompleteSplit(BufferGetPage(parent->buffer))) - ginFinishSplit(btree, parent, false, buildStats); + ginFinishOldSplit(btree, parent, buildStats, GIN_EXCLUSIVE); /* move right if it's needed */ page = BufferGetPage(parent->buffer); @@ -725,7 +725,7 @@ page = BufferGetPage(parent->buffer); if (GinPageIsIncompleteSplit(BufferGetPage(parent->buffer))) - ginFinishSplit(btree, parent, false, buildStats); + ginFinishOldSplit(btree, parent, buildStats, GIN_EXCLUSIVE); } /* insert the downlink */ @@ -762,6 +762,42 @@ } /* + * An entry point to ginFinishSplit() that is used when we stumble upon an + * existing incompletely split page in the tree, as opposed to completing a + * split that we just made outselves. The difference is that stack->buffer may + * be merely share-locked on entry, and will be upgraded to exclusive mode. + * + * Note: Upgrading the lock momentarily releases it. Doing that in a scan + * would not be OK, because a concurrent VACUUM might delete the page while + * we're not holding the lock. It's OK in an insert, though, because VACUUM + * has a different mechanism that prevents it from running concurrently with + * inserts. (Namely, it holds a cleanup lock on the root.) + */ +static void +ginFinishOldSplit(GinBtree btree, GinBtreeStack *stack, GinStatsData *buildStats, int access) +{ + elog(DEBUG1, "finishing incomplete split of block %u in gin index \"%s\"", + stack->blkno, RelationGetRelationName(btree->index)); + + if (access == GIN_SHARE) + { + LockBuffer(stack->buffer, GIN_UNLOCK); + LockBuffer(stack->buffer, GIN_EXCLUSIVE); + + if (!GinPageIsIncompleteSplit(BufferGetPage(stack->buffer))) + { + /* + * Someone else already completed the split while we were not + * holding the lock. + */ + return; + } + } + + ginFinishSplit(btree, stack, false, buildStats); +} + +/* * Insert a value to tree described by stack. * * The value to be inserted is given in 'insertdata'. Its format depends @@ -781,7 +817,7 @@ /* If the leaf page was incompletely split, finish the split first */ if (GinPageIsIncompleteSplit(BufferGetPage(stack->buffer))) - ginFinishSplit(btree, stack, false, buildStats); + ginFinishOldSplit(btree, stack, buildStats, GIN_EXCLUSIVE); done = ginPlaceToPage(btree, stack, insertdata, InvalidBlockNumber, diff -Nru postgresql-13-13.13/src/backend/access/heap/heapam.c postgresql-13-13.14/src/backend/access/heap/heapam.c --- postgresql-13-13.13/src/backend/access/heap/heapam.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/heap/heapam.c 2024-02-05 21:47:02.000000000 +0000 @@ -2646,13 +2646,7 @@ result = TM_Deleted; } - if (crosscheck != InvalidSnapshot && result == TM_Ok) - { - /* Perform additional check for transaction-snapshot mode RI updates */ - if (!HeapTupleSatisfiesVisibility(&tp, crosscheck, buffer)) - result = TM_Updated; - } - + /* sanity check the result HeapTupleSatisfiesUpdate() and the logic above */ if (result != TM_Ok) { Assert(result == TM_SelfModified || @@ -2662,6 +2656,17 @@ Assert(!(tp.t_data->t_infomask & HEAP_XMAX_INVALID)); Assert(result != TM_Updated || !ItemPointerEquals(&tp.t_self, &tp.t_data->t_ctid)); + } + + if (crosscheck != InvalidSnapshot && result == TM_Ok) + { + /* Perform additional check for transaction-snapshot mode RI updates */ + if (!HeapTupleSatisfiesVisibility(&tp, crosscheck, buffer)) + result = TM_Updated; + } + + if (result != TM_Ok) + { tmfd->ctid = tp.t_data->t_ctid; tmfd->xmax = HeapTupleHeaderGetUpdateXid(tp.t_data); if (result == TM_SelfModified) @@ -3289,16 +3294,7 @@ result = TM_Deleted; } - if (crosscheck != InvalidSnapshot && result == TM_Ok) - { - /* Perform additional check for transaction-snapshot mode RI updates */ - if (!HeapTupleSatisfiesVisibility(&oldtup, crosscheck, buffer)) - { - result = TM_Updated; - Assert(!ItemPointerEquals(&oldtup.t_self, &oldtup.t_data->t_ctid)); - } - } - + /* Sanity check the result HeapTupleSatisfiesUpdate() and the logic above */ if (result != TM_Ok) { Assert(result == TM_SelfModified || @@ -3308,6 +3304,17 @@ Assert(!(oldtup.t_data->t_infomask & HEAP_XMAX_INVALID)); Assert(result != TM_Updated || !ItemPointerEquals(&oldtup.t_self, &oldtup.t_data->t_ctid)); + } + + if (crosscheck != InvalidSnapshot && result == TM_Ok) + { + /* Perform additional check for transaction-snapshot mode RI updates */ + if (!HeapTupleSatisfiesVisibility(&oldtup, crosscheck, buffer)) + result = TM_Updated; + } + + if (result != TM_Ok) + { tmfd->ctid = oldtup.t_data->t_ctid; tmfd->xmax = HeapTupleHeaderGetUpdateXid(oldtup.t_data); if (result == TM_SelfModified) diff -Nru postgresql-13-13.13/src/backend/access/heap/hio.c postgresql-13-13.14/src/backend/access/heap/hio.c --- postgresql-13-13.13/src/backend/access/heap/hio.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/heap/hio.c 2024-02-05 21:47:02.000000000 +0000 @@ -363,7 +363,7 @@ * on, as cached in the BulkInsertState or relcache entry. If that * doesn't work, we ask the Free Space Map to locate a suitable page. * Since the FSM's info might be out of date, we have to be prepared to - * loop around and retry multiple times. (To insure this isn't an infinite + * loop around and retry multiple times. (To ensure this isn't an infinite * loop, we must update the FSM with the correct amount of free space on * each page that proves not to be suitable.) If the FSM has no record of * a page with enough free space, we give up and extend the relation. diff -Nru postgresql-13-13.13/src/backend/access/spgist/spgutils.c postgresql-13-13.14/src/backend/access/spgist/spgutils.c --- postgresql-13-13.13/src/backend/access/spgist/spgutils.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/spgist/spgutils.c 2024-02-05 21:47:02.000000000 +0000 @@ -110,8 +110,6 @@ Oid atttype; spgConfigIn in; FmgrInfo *procinfo; - Buffer metabuffer; - SpGistMetaPageData *metadata; cache = MemoryContextAllocZero(index->rd_indexcxt, sizeof(SpGistCache)); @@ -156,19 +154,28 @@ fillTypeDesc(&cache->attPrefixType, cache->config.prefixType); fillTypeDesc(&cache->attLabelType, cache->config.labelType); - /* Last, get the lastUsedPages data from the metapage */ - metabuffer = ReadBuffer(index, SPGIST_METAPAGE_BLKNO); - LockBuffer(metabuffer, BUFFER_LOCK_SHARE); + /* + * Finally, if it's a real index (not a partitioned one), get the + * lastUsedPages data from the metapage + */ + if (index->rd_rel->relkind != RELKIND_PARTITIONED_INDEX) + { + Buffer metabuffer; + SpGistMetaPageData *metadata; - metadata = SpGistPageGetMeta(BufferGetPage(metabuffer)); + metabuffer = ReadBuffer(index, SPGIST_METAPAGE_BLKNO); + LockBuffer(metabuffer, BUFFER_LOCK_SHARE); - if (metadata->magicNumber != SPGIST_MAGIC_NUMBER) - elog(ERROR, "index \"%s\" is not an SP-GiST index", - RelationGetRelationName(index)); + metadata = SpGistPageGetMeta(BufferGetPage(metabuffer)); - cache->lastUsedPages = metadata->lastUsedPages; + if (metadata->magicNumber != SPGIST_MAGIC_NUMBER) + elog(ERROR, "index \"%s\" is not an SP-GiST index", + RelationGetRelationName(index)); - UnlockReleaseBuffer(metabuffer); + cache->lastUsedPages = metadata->lastUsedPages; + + UnlockReleaseBuffer(metabuffer); + } index->rd_amcache = (void *) cache; } diff -Nru postgresql-13-13.13/src/backend/access/transam/twophase.c postgresql-13-13.14/src/backend/access/transam/twophase.c --- postgresql-13-13.13/src/backend/access/transam/twophase.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/transam/twophase.c 2024-02-05 21:47:02.000000000 +0000 @@ -484,7 +484,7 @@ proc->roleId = owner; proc->tempNamespaceId = InvalidOid; proc->isBackgroundWorker = false; - proc->lwWaiting = false; + proc->lwWaiting = LW_WS_NOT_WAITING; proc->lwWaitMode = 0; proc->waitLock = NULL; proc->waitProcLock = NULL; diff -Nru postgresql-13-13.13/src/backend/access/transam/xact.c postgresql-13-13.14/src/backend/access/transam/xact.c --- postgresql-13-13.13/src/backend/access/transam/xact.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/transam/xact.c 2024-02-05 21:47:02.000000000 +0000 @@ -5180,6 +5180,7 @@ s->blockState = TBLOCK_SUBBEGIN; GetUserIdAndSecContext(&s->prevUser, &s->prevSecContext); s->prevXactReadOnly = XactReadOnly; + s->startedInRecovery = p->startedInRecovery; s->parallelModeLevel = 0; CurrentTransactionState = s; diff -Nru postgresql-13-13.13/src/backend/access/transam/xlog.c postgresql-13-13.14/src/backend/access/transam/xlog.c --- postgresql-13-13.13/src/backend/access/transam/xlog.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/access/transam/xlog.c 2024-02-05 21:47:02.000000000 +0000 @@ -1235,8 +1235,10 @@ if (!debug_reader) debug_reader = XLogReaderAllocate(wal_segment_size, NULL, - XL_ROUTINE(), NULL); - + XL_ROUTINE(.page_read = NULL, + .segment_open = NULL, + .segment_close = NULL), + NULL); if (!debug_reader) { appendStringInfoString(&buf, "error decoding record: out of memory"); diff -Nru postgresql-13-13.13/src/backend/catalog/aclchk.c postgresql-13-13.14/src/backend/catalog/aclchk.c --- postgresql-13-13.13/src/backend/catalog/aclchk.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/catalog/aclchk.c 2024-02-05 21:47:02.000000000 +0000 @@ -5687,9 +5687,9 @@ ReleaseSysCache(tuple); } - /* pg_largeobject_metadata */ - else if (classoid == LargeObjectMetadataRelationId) + else if (classoid == LargeObjectRelationId) { + /* For large objects, we must consult pg_largeobject_metadata */ Datum aclDatum; bool isNull; HeapTuple tuple; diff -Nru postgresql-13-13.13/src/backend/catalog/heap.c postgresql-13-13.14/src/backend/catalog/heap.c --- postgresql-13-13.13/src/backend/catalog/heap.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/catalog/heap.c 2024-02-05 21:47:02.000000000 +0000 @@ -2612,7 +2612,8 @@ continue; /* If the DEFAULT is volatile we cannot use a missing value */ - if (colDef->missingMode && contain_volatile_functions((Node *) expr)) + if (colDef->missingMode && + contain_volatile_functions_after_planning((Expr *) expr)) colDef->missingMode = false; defOid = StoreAttrDefault(rel, colDef->attnum, expr, is_internal, @@ -3047,9 +3048,11 @@ if (attgenerated) { + /* Disallow refs to other generated columns */ check_nested_generated(pstate, expr); - if (contain_mutable_functions(expr)) + /* Disallow mutable functions */ + if (contain_mutable_functions_after_planning((Expr *) expr)) ereport(ERROR, (errcode(ERRCODE_INVALID_OBJECT_DEFINITION), errmsg("generation expression is not immutable"))); diff -Nru postgresql-13-13.13/src/backend/commands/alter.c postgresql-13-13.14/src/backend/commands/alter.c --- postgresql-13-13.13/src/backend/commands/alter.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/alter.c 2024-02-05 21:47:02.000000000 +0000 @@ -1044,9 +1044,14 @@ /* Perform actual update */ CatalogTupleUpdate(rel, &newtup->t_self, newtup); - /* Update owner dependency reference */ + /* + * Update owner dependency reference. When working on a large object, + * we have to translate back to the OID conventionally used for LOs' + * classId. + */ if (classId == LargeObjectMetadataRelationId) classId = LargeObjectRelationId; + changeDependencyOnOwner(classId, objectId, new_ownerId); /* Release memory */ @@ -1054,6 +1059,16 @@ pfree(nulls); pfree(replaces); } + else + { + /* + * No need to change anything. But when working on a large object, we + * have to translate back to the OID conventionally used for LOs' + * classId, or the post-alter hook (if any) will get confused. + */ + if (classId == LargeObjectMetadataRelationId) + classId = LargeObjectRelationId; + } InvokeObjectPostAlterHook(classId, objectId, 0); } diff -Nru postgresql-13-13.13/src/backend/commands/copy.c postgresql-13-13.14/src/backend/commands/copy.c --- postgresql-13-13.13/src/backend/commands/copy.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/copy.c 2024-02-05 21:47:02.000000000 +0000 @@ -2893,6 +2893,9 @@ * Can't support multi-inserts if there are any volatile function * expressions in WHERE clause. Similarly to the trigger case above, * such expressions may query the table we're inserting into. + * + * Note: the whereClause was already preprocessed in DoCopy(), so it's + * okay to use contain_volatile_functions() directly. */ insertMethod = CIM_SINGLE; } @@ -3441,7 +3444,8 @@ * known to be safe for use with the multi-insert * optimization. Hence we use this special case function * checker rather than the standard check for - * contain_volatile_functions(). + * contain_volatile_functions(). Note also that we already + * ran the expression through expression_planner(). */ if (!volatile_defexprs) volatile_defexprs = contain_volatile_functions_not_nextval((Node *) defexpr); diff -Nru postgresql-13-13.13/src/backend/commands/indexcmds.c postgresql-13-13.14/src/backend/commands/indexcmds.c --- postgresql-13-13.13/src/backend/commands/indexcmds.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/indexcmds.c 2024-02-05 21:47:02.000000000 +0000 @@ -984,10 +984,13 @@ { if (key->partattrs[i] == indexInfo->ii_IndexAttrNumbers[j]) { - /* Matched the column, now what about the equality op? */ + /* Matched the column, now what about the collation and equality op? */ Oid idx_opfamily; Oid idx_opcintype; + if (key->partcollation[i] != collationObjectId[j]) + continue; + if (get_opclass_opfamily_and_input_type(classObjectId[j], &idx_opfamily, &idx_opcintype)) @@ -1668,33 +1671,6 @@ /* - * CheckMutability - * Test whether given expression is mutable - */ -static bool -CheckMutability(Expr *expr) -{ - /* - * First run the expression through the planner. This has a couple of - * important consequences. First, function default arguments will get - * inserted, which may affect volatility (consider "default now()"). - * Second, inline-able functions will get inlined, which may allow us to - * conclude that the function is really less volatile than it's marked. As - * an example, polymorphic functions must be marked with the most volatile - * behavior that they have for any input type, but once we inline the - * function we may be able to conclude that it's not so volatile for the - * particular input type we're dealing with. - * - * We assume here that expression_planner() won't scribble on its input. - */ - expr = expression_planner(expr); - - /* Now we can search for non-immutable functions */ - return contain_mutable_functions((Node *) expr); -} - - -/* * CheckPredicate * Checks that the given partial-index predicate is valid. * @@ -1717,7 +1693,7 @@ * A predicate using mutable functions is probably wrong, for the same * reasons that we don't allow an index expression to use one. */ - if (CheckMutability(predicate)) + if (contain_mutable_functions_after_planning(predicate)) ereport(ERROR, (errcode(ERRCODE_INVALID_OBJECT_DEFINITION), errmsg("functions in index predicate must be marked IMMUTABLE"))); @@ -1860,7 +1836,7 @@ * same data every time, it's not clear what the index entries * mean at all. */ - if (CheckMutability((Expr *) expr)) + if (contain_mutable_functions_after_planning((Expr *) expr)) ereport(ERROR, (errcode(ERRCODE_INVALID_OBJECT_DEFINITION), errmsg("functions in index expression must be marked IMMUTABLE"))); diff -Nru postgresql-13-13.13/src/backend/commands/matview.c postgresql-13-13.14/src/backend/commands/matview.c --- postgresql-13-13.13/src/backend/commands/matview.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/matview.c 2024-02-05 21:47:02.000000000 +0000 @@ -644,13 +644,35 @@ SPI_getvalue(SPI_tuptable->vals[0], SPI_tuptable->tupdesc, 1)))); } + /* + * Create the temporary "diff" table. + * + * Temporarily switch out of the SECURITY_RESTRICTED_OPERATION context, + * because you cannot create temp tables in SRO context. For extra + * paranoia, add the composite type column only after switching back to + * SRO context. + */ SetUserIdAndSecContext(relowner, save_sec_context | SECURITY_LOCAL_USERID_CHANGE); + resetStringInfo(&querybuf); + appendStringInfo(&querybuf, + "CREATE TEMP TABLE %s (tid pg_catalog.tid)", + diffname); + if (SPI_exec(querybuf.data, 0) != SPI_OK_UTILITY) + elog(ERROR, "SPI_exec failed: %s", querybuf.data); + SetUserIdAndSecContext(relowner, + save_sec_context | SECURITY_RESTRICTED_OPERATION); + resetStringInfo(&querybuf); + appendStringInfo(&querybuf, + "ALTER TABLE %s ADD COLUMN newdata %s", + diffname, tempname); + if (SPI_exec(querybuf.data, 0) != SPI_OK_UTILITY) + elog(ERROR, "SPI_exec failed: %s", querybuf.data); - /* Start building the query for creating the diff table. */ + /* Start building the query for populating the diff table. */ resetStringInfo(&querybuf); appendStringInfo(&querybuf, - "CREATE TEMP TABLE %s AS " + "INSERT INTO %s " "SELECT mv.ctid AS tid, newdata.*::%s AS newdata " "FROM %s mv FULL JOIN %s newdata ON (", diffname, tempname, matviewname, tempname); @@ -770,22 +792,22 @@ * * ExecRefreshMatView() checks that after taking the exclusive lock on the * matview. So at least one unique index is guaranteed to exist here - * because the lock is still being held; so an Assert seems sufficient. + * because the lock is still being held. (One known exception is if a + * function called as part of refreshing the matview drops the index. + * That's a pretty silly thing to do.) */ - Assert(foundUniqueIndex); + if (!foundUniqueIndex) + elog(ERROR, "could not find suitable unique index on materialized view"); appendStringInfoString(&querybuf, " AND newdata.* OPERATOR(pg_catalog.*=) mv.*) " "WHERE newdata.* IS NULL OR mv.* IS NULL " "ORDER BY tid"); - /* Create the temporary "diff" table. */ - if (SPI_exec(querybuf.data, 0) != SPI_OK_UTILITY) + /* Populate the temporary "diff" table. */ + if (SPI_exec(querybuf.data, 0) != SPI_OK_INSERT) elog(ERROR, "SPI_exec failed: %s", querybuf.data); - SetUserIdAndSecContext(relowner, - save_sec_context | SECURITY_RESTRICTED_OPERATION); - /* * We have no further use for data from the "full-data" temp table, but we * must keep it around because its type is referenced from the diff table. diff -Nru postgresql-13-13.13/src/backend/commands/statscmds.c postgresql-13-13.14/src/backend/commands/statscmds.c --- postgresql-13-13.13/src/backend/commands/statscmds.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/statscmds.c 2024-02-05 21:47:02.000000000 +0000 @@ -538,20 +538,14 @@ } /* - * Guts of statistics object deletion. - */ -void -RemoveStatisticsById(Oid statsOid) +* Guts of statistics object deletion. +*/ +static void +RemoveStatisticsDataById(Oid statsOid) { Relation relation; HeapTuple tup; - Form_pg_statistic_ext statext; - Oid relid; - /* - * First delete the pg_statistic_ext_data tuple holding the actual - * statistical data. - */ relation = table_open(StatisticExtDataRelationId, RowExclusiveLock); tup = SearchSysCache1(STATEXTDATASTXOID, ObjectIdGetDatum(statsOid)); @@ -564,6 +558,19 @@ ReleaseSysCache(tup); table_close(relation, RowExclusiveLock); +} + +/* + * Guts of statistics object deletion. + */ +void +RemoveStatisticsById(Oid statsOid) +{ + Relation relation; + Relation rel; + HeapTuple tup; + Form_pg_statistic_ext statext; + Oid relid; /* * Delete the pg_statistic_ext tuple. Also send out a cache inval on the @@ -579,12 +586,24 @@ statext = (Form_pg_statistic_ext) GETSTRUCT(tup); relid = statext->stxrelid; + /* + * Delete the pg_statistic_ext_data tuple holding the actual statistical + * data. We lock the user table first, to prevent other processes (e.g. + * DROP STATISTICS) from removing the row concurrently. + */ + rel = table_open(relid, ShareUpdateExclusiveLock); + + RemoveStatisticsDataById(statsOid); + CacheInvalidateRelcacheByRelid(relid); CatalogTupleDelete(relation, &tup->t_self); ReleaseSysCache(tup); + /* Keep lock until the end of the transaction. */ + table_close(rel, NoLock); + table_close(relation, RowExclusiveLock); } diff -Nru postgresql-13-13.13/src/backend/commands/tablecmds.c postgresql-13-13.14/src/backend/commands/tablecmds.c --- postgresql-13-13.13/src/backend/commands/tablecmds.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/tablecmds.c 2024-02-05 21:47:02.000000000 +0000 @@ -6291,6 +6291,10 @@ colDef->colname, RelationGetRelationName(rel)))); table_close(attrdesc, RowExclusiveLock); + + /* Make the child column change visible */ + CommandCounterIncrement(); + return InvalidObjectAddress; } } @@ -10556,15 +10560,19 @@ /* * transformFkeyCheckAttrs - * - * Make sure that the attributes of a referenced table belong to a unique - * (or primary key) constraint. Return the OID of the index supporting - * the constraint, as well as the opclasses associated with the index - * columns. + * Validate that the 'attnums' columns in the 'pkrel' relation are valid to + * reference as part of a foreign key constraint. + * + * Returns the OID of the unique index supporting the constraint and + * populates the caller-provided 'opclasses' array with the opclasses + * associated with the index columns. + * + * Raises an ERROR on validation failure. */ static Oid transformFkeyCheckAttrs(Relation pkrel, int numattrs, int16 *attnums, - Oid *opclasses) /* output parameter */ + Oid *opclasses) { Oid indexoid = InvalidOid; bool found = false; @@ -16356,30 +16364,6 @@ *partexprs = lappend(*partexprs, expr); /* - * Try to simplify the expression before checking for - * mutability. The main practical value of doing it in this - * order is that an inline-able SQL-language function will be - * accepted if its expansion is immutable, whether or not the - * function itself is marked immutable. - * - * Note that expression_planner does not change the passed in - * expression destructively and we have already saved the - * expression to be stored into the catalog above. - */ - expr = (Node *) expression_planner((Expr *) expr); - - /* - * Partition expression cannot contain mutable functions, - * because a given row must always map to the same partition - * as long as there is no change in the partition boundary - * structure. - */ - if (contain_mutable_functions(expr)) - ereport(ERROR, - (errcode(ERRCODE_INVALID_OBJECT_DEFINITION), - errmsg("functions in partition key expression must be marked IMMUTABLE"))); - - /* * transformPartitionSpec() should have already rejected * subqueries, aggregates, window functions, and SRFs, based * on the EXPR_KIND_ for partition expressions. @@ -16421,6 +16405,32 @@ } /* + * Preprocess the expression before checking for mutability. + * This is essential for the reasons described in + * contain_mutable_functions_after_planning. However, we call + * expression_planner for ourselves rather than using that + * function, because if constant-folding reduces the + * expression to a constant, we'd like to know that so we can + * complain below. + * + * Like contain_mutable_functions_after_planning, assume that + * expression_planner won't scribble on its input, so this + * won't affect the partexprs entry we saved above. + */ + expr = (Node *) expression_planner((Expr *) expr); + + /* + * Partition expressions cannot contain mutable functions, + * because a given row must always map to the same partition + * as long as there is no change in the partition boundary + * structure. + */ + if (contain_mutable_functions(expr)) + ereport(ERROR, + (errcode(ERRCODE_INVALID_OBJECT_DEFINITION), + errmsg("functions in partition key expression must be marked IMMUTABLE"))); + + /* * While it is not exactly *wrong* for a partition expression * to be a constant, it seems better to reject such keys. */ diff -Nru postgresql-13-13.13/src/backend/commands/tsearchcmds.c postgresql-13-13.14/src/backend/commands/tsearchcmds.c --- postgresql-13-13.13/src/backend/commands/tsearchcmds.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/commands/tsearchcmds.c 2024-02-05 21:47:02.000000000 +0000 @@ -48,6 +48,12 @@ #include "utils/rel.h" #include "utils/syscache.h" +/* Single entry of List returned by getTokenTypes() */ +typedef struct +{ + int num; /* token type number */ + char *name; /* token type name */ +} TSTokenTypeItem; static void MakeConfigurationMapping(AlterTSConfigurationStmt *stmt, HeapTuple tup, Relation relMap); @@ -1224,22 +1230,45 @@ } /* - * Translate a list of token type names to an array of token type numbers + * Check whether a token type name is a member of a TSTokenTypeItem list. */ -static int * +static bool +tstoken_list_member(char *token_name, List *tokens) +{ + ListCell *c; + bool found = false; + + foreach(c, tokens) + { + TSTokenTypeItem *ts = (TSTokenTypeItem *) lfirst(c); + + if (strcmp(token_name, ts->name) == 0) + { + found = true; + break; + } + } + + return found; +} + +/* + * Translate a list of token type names to a list of unique TSTokenTypeItem. + * + * Duplicated entries list are removed from tokennames. + */ +static List * getTokenTypes(Oid prsId, List *tokennames) { TSParserCacheEntry *prs = lookup_ts_parser_cache(prsId); LexDescr *list; - int *res, - i, - ntoken; + List *result = NIL; + int ntoken; ListCell *tn; ntoken = list_length(tokennames); if (ntoken == 0) - return NULL; - res = (int *) palloc(sizeof(int) * ntoken); + return NIL; if (!OidIsValid(prs->lextypeOid)) elog(ERROR, "method lextype isn't defined for text search parser %u", @@ -1249,19 +1278,26 @@ list = (LexDescr *) DatumGetPointer(OidFunctionCall1(prs->lextypeOid, (Datum) 0)); - i = 0; foreach(tn, tokennames) { Value *val = (Value *) lfirst(tn); bool found = false; int j; + /* Skip if this token is already in the result */ + if (tstoken_list_member(strVal(val), result)) + continue; + j = 0; while (list && list[j].lexid) { if (strcmp(strVal(val), list[j].alias) == 0) { - res[i] = list[j].lexid; + TSTokenTypeItem *ts = (TSTokenTypeItem *) palloc0(sizeof(TSTokenTypeItem)); + + ts->num = list[j].lexid; + ts->name = pstrdup(strVal(val)); + result = lappend(result, ts); found = true; break; } @@ -1272,10 +1308,9 @@ (errcode(ERRCODE_INVALID_PARAMETER_VALUE), errmsg("token type \"%s\" does not exist", strVal(val)))); - i++; } - return res; + return result; } /* @@ -1293,8 +1328,7 @@ int i; int j; Oid prsId; - int *tokens, - ntoken; + List *tokens = NIL; Oid *dictIds; int ndict; ListCell *c; @@ -1304,15 +1338,16 @@ prsId = tsform->cfgparser; tokens = getTokenTypes(prsId, stmt->tokentype); - ntoken = list_length(stmt->tokentype); if (stmt->override) { /* * delete maps for tokens if they exist and command was ALTER */ - for (i = 0; i < ntoken; i++) + foreach(c, tokens) { + TSTokenTypeItem *ts = (TSTokenTypeItem *) lfirst(c); + ScanKeyInit(&skey[0], Anum_pg_ts_config_map_mapcfg, BTEqualStrategyNumber, F_OIDEQ, @@ -1320,7 +1355,7 @@ ScanKeyInit(&skey[1], Anum_pg_ts_config_map_maptokentype, BTEqualStrategyNumber, F_INT4EQ, - Int32GetDatum(tokens[i])); + Int32GetDatum(ts->num)); scan = systable_beginscan(relMap, TSConfigMapIndexId, true, NULL, 2, skey); @@ -1375,9 +1410,11 @@ { bool tokmatch = false; - for (j = 0; j < ntoken; j++) + foreach(c, tokens) { - if (cfgmap->maptokentype == tokens[j]) + TSTokenTypeItem *ts = (TSTokenTypeItem *) lfirst(c); + + if (cfgmap->maptokentype == ts->num) { tokmatch = true; break; @@ -1418,8 +1455,10 @@ /* * Insertion of new entries */ - for (i = 0; i < ntoken; i++) + foreach(c, tokens) { + TSTokenTypeItem *ts = (TSTokenTypeItem *) lfirst(c); + for (j = 0; j < ndict; j++) { Datum values[Natts_pg_ts_config_map]; @@ -1427,7 +1466,7 @@ memset(nulls, false, sizeof(nulls)); values[Anum_pg_ts_config_map_mapcfg - 1] = ObjectIdGetDatum(cfgId); - values[Anum_pg_ts_config_map_maptokentype - 1] = Int32GetDatum(tokens[i]); + values[Anum_pg_ts_config_map_maptokentype - 1] = Int32GetDatum(ts->num); values[Anum_pg_ts_config_map_mapseqno - 1] = Int32GetDatum(j + 1); values[Anum_pg_ts_config_map_mapdict - 1] = ObjectIdGetDatum(dictIds[j]); @@ -1454,9 +1493,8 @@ ScanKeyData skey[2]; SysScanDesc scan; HeapTuple maptup; - int i; Oid prsId; - int *tokens; + List *tokens = NIL; ListCell *c; tsform = (Form_pg_ts_config) GETSTRUCT(tup); @@ -1465,10 +1503,9 @@ tokens = getTokenTypes(prsId, stmt->tokentype); - i = 0; - foreach(c, stmt->tokentype) + foreach(c, tokens) { - Value *val = (Value *) lfirst(c); + TSTokenTypeItem *ts = (TSTokenTypeItem *) lfirst(c); bool found = false; ScanKeyInit(&skey[0], @@ -1478,7 +1515,7 @@ ScanKeyInit(&skey[1], Anum_pg_ts_config_map_maptokentype, BTEqualStrategyNumber, F_INT4EQ, - Int32GetDatum(tokens[i])); + Int32GetDatum(ts->num)); scan = systable_beginscan(relMap, TSConfigMapIndexId, true, NULL, 2, skey); @@ -1498,17 +1535,15 @@ ereport(ERROR, (errcode(ERRCODE_UNDEFINED_OBJECT), errmsg("mapping for token type \"%s\" does not exist", - strVal(val)))); + ts->name))); } else { ereport(NOTICE, (errmsg("mapping for token type \"%s\" does not exist, skipping", - strVal(val)))); + ts->name))); } } - - i++; } EventTriggerCollectAlterTSConfig(stmt, cfgId, NULL, 0); diff -Nru postgresql-13-13.13/src/backend/executor/nodeHash.c postgresql-13-13.14/src/backend/executor/nodeHash.c --- postgresql-13-13.13/src/backend/executor/nodeHash.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/executor/nodeHash.c 2024-02-05 21:47:02.000000000 +0000 @@ -1162,6 +1162,7 @@ double dtuples; double dbuckets; int new_nbuckets; + uint32 max_buckets; /* * We probably also need a smaller bucket array. How many @@ -1174,9 +1175,17 @@ * array. */ dtuples = (old_batch0->ntuples * 2.0) / new_nbatch; + + /* + * We need to calculate the maximum number of buckets to + * stay within the MaxAllocSize boundary. Round the + * maximum number to the previous power of 2 given that + * later we round the number to the next power of 2. + */ + max_buckets = pg_prevpower2_32((uint32) + (MaxAllocSize / sizeof(dsa_pointer_atomic))); dbuckets = ceil(dtuples / NTUP_PER_BUCKET); - dbuckets = Min(dbuckets, - MaxAllocSize / sizeof(dsa_pointer_atomic)); + dbuckets = Min(dbuckets, max_buckets); new_nbuckets = (int) dbuckets; new_nbuckets = Max(new_nbuckets, 1024); new_nbuckets = pg_nextpower2_32(new_nbuckets); diff -Nru postgresql-13-13.13/src/backend/jit/llvm/llvmjit.c postgresql-13-13.14/src/backend/jit/llvm/llvmjit.c --- postgresql-13-13.13/src/backend/jit/llvm/llvmjit.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/jit/llvm/llvmjit.c 2024-02-05 21:47:02.000000000 +0000 @@ -47,6 +47,8 @@ #include "utils/memutils.h" #include "utils/resowner_private.h" +#define LLVMJIT_LLVM_CONTEXT_REUSE_MAX 100 + /* Handle of a module emitted via ORC JIT */ typedef struct LLVMJitHandle { @@ -99,8 +101,15 @@ static bool llvm_session_initialized = false; static size_t llvm_generation = 0; + +/* number of LLVMJitContexts that currently are in use */ +static size_t llvm_jit_context_in_use_count = 0; + +/* how many times has the current LLVMContextRef been used */ +static size_t llvm_llvm_context_reuse_count = 0; static const char *llvm_triple = NULL; static const char *llvm_layout = NULL; +static LLVMContextRef llvm_context; static LLVMTargetRef llvm_targetref; @@ -121,6 +130,8 @@ static void llvm_optimize_module(LLVMJitContext *context, LLVMModuleRef module); static void llvm_create_types(void); +static void llvm_set_target(void); +static void llvm_recreate_llvm_context(void); static uint64_t llvm_resolve_symbol(const char *name, void *ctx); #if LLVM_VERSION_MAJOR > 11 @@ -142,6 +153,63 @@ cb->compile_expr = llvm_compile_expr; } + +/* + * Every now and then create a new LLVMContextRef. Unfortunately, during every + * round of inlining, types may "leak" (they can still be found/used via the + * context, but new types will be created the next time in inlining is + * performed). To prevent that from slowly accumulating problematic amounts of + * memory, recreate the LLVMContextRef we use. We don't want to do so too + * often, as that implies some overhead (particularly re-loading the module + * summaries / modules is fairly expensive). A future TODO would be to make + * this more finegrained and only drop/recreate the LLVMContextRef when we know + * there has been inlining. If we can get the size of the context from LLVM + * then that might be a better way to determine when to drop/recreate rather + * then the usagecount heuristic currently employed. + */ +static void +llvm_recreate_llvm_context(void) +{ + if (!llvm_context) + elog(ERROR, "Trying to recreate a non-existing context"); + + /* + * We can only safely recreate the LLVM context if no other code is being + * JITed, otherwise we'd release the types in use for that. + */ + if (llvm_jit_context_in_use_count > 0) + { + llvm_llvm_context_reuse_count++; + return; + } + + if (llvm_llvm_context_reuse_count <= LLVMJIT_LLVM_CONTEXT_REUSE_MAX) + { + llvm_llvm_context_reuse_count++; + return; + } + + /* + * Need to reset the modules that the inlining code caches before + * disposing of the context. LLVM modules exist within a specific LLVM + * context, therefore disposing of the context before resetting the cache + * would lead to dangling pointers to modules. + */ + llvm_inline_reset_caches(); + + LLVMContextDispose(llvm_context); + llvm_context = LLVMContextCreate(); + llvm_llvm_context_reuse_count = 0; + + /* + * Re-build cached type information, so code generation code can rely on + * that information to be present (also prevents the variables to be + * dangling references). + */ + llvm_create_types(); +} + + /* * Create a context for JITing work. * @@ -158,6 +226,8 @@ llvm_session_initialize(); + llvm_recreate_llvm_context(); + ResourceOwnerEnlargeJIT(CurrentResourceOwner); context = MemoryContextAllocZero(TopMemoryContext, @@ -168,6 +238,8 @@ context->base.resowner = CurrentResourceOwner; ResourceOwnerRememberJIT(CurrentResourceOwner, PointerGetDatum(context)); + llvm_jit_context_in_use_count++; + return context; } @@ -177,10 +249,16 @@ static void llvm_release_context(JitContext *context) { - LLVMJitContext *llvm_context = (LLVMJitContext *) context; + LLVMJitContext *llvm_jit_context = (LLVMJitContext *) context; ListCell *lc; /* + * Consider as cleaned up even if we skip doing so below, that way we can + * verify the tracking is correct (see llvm_shutdown()). + */ + llvm_jit_context_in_use_count--; + + /* * When this backend is exiting, don't clean up LLVM. As an error might * have occurred from within LLVM, we do not want to risk reentering. All * resource cleanup is going to happen through process exit. @@ -190,13 +268,13 @@ llvm_enter_fatal_on_oom(); - if (llvm_context->module) + if (llvm_jit_context->module) { - LLVMDisposeModule(llvm_context->module); - llvm_context->module = NULL; + LLVMDisposeModule(llvm_jit_context->module); + llvm_jit_context->module = NULL; } - foreach(lc, llvm_context->handles) + foreach(lc, llvm_jit_context->handles) { LLVMJitHandle *jit_handle = (LLVMJitHandle *) lfirst(lc); @@ -226,8 +304,8 @@ pfree(jit_handle); } - list_free(llvm_context->handles); - llvm_context->handles = NIL; + list_free(llvm_jit_context->handles); + llvm_jit_context->handles = NIL; llvm_leave_fatal_on_oom(); } @@ -247,7 +325,7 @@ { context->compiled = false; context->module_generation = llvm_generation++; - context->module = LLVMModuleCreateWithName("pg"); + context->module = LLVMModuleCreateWithNameInContext("pg", llvm_context); LLVMSetTarget(context->module, llvm_triple); LLVMSetDataLayout(context->module, llvm_layout); } @@ -831,6 +909,14 @@ LLVMInitializeNativeAsmPrinter(); LLVMInitializeNativeAsmParser(); + if (llvm_context == NULL) + { + llvm_context = LLVMContextCreate(); + + llvm_jit_context_in_use_count = 0; + llvm_llvm_context_reuse_count = 0; + } + /* * When targeting LLVM 15, turn off opaque pointers for the context we * build our code in. We don't need to do so for other contexts (e.g. @@ -850,6 +936,11 @@ */ llvm_create_types(); + /* + * Extract target information from loaded module. + */ + llvm_set_target(); + if (LLVMGetTargetFromTriple(llvm_triple, &llvm_targetref, &error) != 0) { elog(FATAL, "failed to query triple %s", error); @@ -921,7 +1012,7 @@ } #endif /* LLVM_VERSION_MAJOR > 11 */ - before_shmem_exit(llvm_shutdown, 0); + on_proc_exit(llvm_shutdown, 0); llvm_session_initialized = true; @@ -945,6 +1036,10 @@ return; } + if (llvm_jit_context_in_use_count != 0) + elog(PANIC, "LLVMJitContext in use count not 0 at exit (is %zu)", + llvm_jit_context_in_use_count); + #if LLVM_VERSION_MAJOR > 11 { if (llvm_opt3_orc) @@ -1008,6 +1103,23 @@ } /* + * Load triple & layout from clang emitted file so we're guaranteed to be + * compatible. + */ +static void +llvm_set_target(void) +{ + if (!llvm_types_module) + elog(ERROR, "failed to extract target information, llvmjit_types.c not loaded"); + + if (llvm_triple == NULL) + llvm_triple = pstrdup(LLVMGetTarget(llvm_types_module)); + + if (llvm_layout == NULL) + llvm_layout = pstrdup(LLVMGetDataLayoutStr(llvm_types_module)); +} + +/* * Load required information, types, function signatures from llvmjit_types.c * and make them available in global variables. * @@ -1030,19 +1142,12 @@ } /* eagerly load contents, going to need it all */ - if (LLVMParseBitcode2(buf, &llvm_types_module)) + if (LLVMParseBitcodeInContext2(llvm_context, buf, &llvm_types_module)) { - elog(ERROR, "LLVMParseBitcode2 of %s failed", path); + elog(ERROR, "LLVMParseBitcodeInContext2 of %s failed", path); } LLVMDisposeMemoryBuffer(buf); - /* - * Load triple & layout from clang emitted file so we're guaranteed to be - * compatible. - */ - llvm_triple = pstrdup(LLVMGetTarget(llvm_types_module)); - llvm_layout = pstrdup(LLVMGetDataLayoutStr(llvm_types_module)); - TypeSizeT = llvm_pg_var_type("TypeSizeT"); TypeParamBool = load_return_type(llvm_types_module, "FunctionReturningBool"); TypeStorageBool = llvm_pg_var_type("TypeStorageBool"); diff -Nru postgresql-13-13.13/src/backend/jit/llvm/llvmjit_deform.c postgresql-13-13.14/src/backend/jit/llvm/llvmjit_deform.c --- postgresql-13-13.13/src/backend/jit/llvm/llvmjit_deform.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/jit/llvm/llvmjit_deform.c 2024-02-05 21:47:02.000000000 +0000 @@ -37,6 +37,7 @@ char *funcname; LLVMModuleRef mod; + LLVMContextRef lc; LLVMBuilderRef b; LLVMTypeRef deform_sig; @@ -99,6 +100,7 @@ return NULL; mod = llvm_mutable_module(context); + lc = LLVMGetModuleContext(mod); funcname = llvm_expand_funcname(context, "deform"); @@ -133,8 +135,8 @@ param_types[0] = l_ptr(StructTupleTableSlot); - deform_sig = LLVMFunctionType(LLVMVoidType(), param_types, - lengthof(param_types), 0); + deform_sig = LLVMFunctionType(LLVMVoidTypeInContext(lc), + param_types, lengthof(param_types), 0); } v_deform_fn = LLVMAddFunction(mod, funcname, deform_sig); LLVMSetLinkage(v_deform_fn, LLVMInternalLinkage); @@ -142,17 +144,17 @@ llvm_copy_attributes(AttributeTemplate, v_deform_fn); b_entry = - LLVMAppendBasicBlock(v_deform_fn, "entry"); + LLVMAppendBasicBlockInContext(lc, v_deform_fn, "entry"); b_adjust_unavail_cols = - LLVMAppendBasicBlock(v_deform_fn, "adjust_unavail_cols"); + LLVMAppendBasicBlockInContext(lc, v_deform_fn, "adjust_unavail_cols"); b_find_start = - LLVMAppendBasicBlock(v_deform_fn, "find_startblock"); + LLVMAppendBasicBlockInContext(lc, v_deform_fn, "find_startblock"); b_out = - LLVMAppendBasicBlock(v_deform_fn, "outblock"); + LLVMAppendBasicBlockInContext(lc, v_deform_fn, "outblock"); b_dead = - LLVMAppendBasicBlock(v_deform_fn, "deadblock"); + LLVMAppendBasicBlockInContext(lc, v_deform_fn, "deadblock"); - b = LLVMCreateBuilder(); + b = LLVMCreateBuilderInContext(lc); attcheckattnoblocks = palloc(sizeof(LLVMBasicBlockRef) * natts); attstartblocks = palloc(sizeof(LLVMBasicBlockRef) * natts); @@ -233,7 +235,7 @@ v_tuplep, FIELDNO_HEAPTUPLEHEADERDATA_BITS, ""), - l_ptr(LLVMInt8Type()), + l_ptr(LLVMInt8TypeInContext(lc)), "t_bits"); v_infomask1 = l_load_struct_gep(b, @@ -251,14 +253,14 @@ v_hasnulls = LLVMBuildICmp(b, LLVMIntNE, LLVMBuildAnd(b, - l_int16_const(HEAP_HASNULL), + l_int16_const(lc, HEAP_HASNULL), v_infomask1, ""), - l_int16_const(0), + l_int16_const(lc, 0), "hasnulls"); /* t_infomask2 & HEAP_NATTS_MASK */ v_maxatt = LLVMBuildAnd(b, - l_int16_const(HEAP_NATTS_MASK), + l_int16_const(lc, HEAP_NATTS_MASK), v_infomask2, "maxatt"); @@ -273,13 +275,13 @@ v_tuplep, FIELDNO_HEAPTUPLEHEADERDATA_HOFF, ""), - LLVMInt32Type(), "t_hoff"); + LLVMInt32TypeInContext(lc), "t_hoff"); v_tupdata_base = l_gep(b, - LLVMInt8Type(), + LLVMInt8TypeInContext(lc), LLVMBuildBitCast(b, v_tuplep, - l_ptr(LLVMInt8Type()), + l_ptr(LLVMInt8TypeInContext(lc)), ""), &v_hoff, 1, "v_tupdata_base"); @@ -291,7 +293,7 @@ { LLVMValueRef v_off_start; - v_off_start = l_load(b, LLVMInt32Type(), v_slotoffp, "v_slot_off"); + v_off_start = l_load(b, LLVMInt32TypeInContext(lc), v_slotoffp, "v_slot_off"); v_off_start = LLVMBuildZExt(b, v_off_start, TypeSizeT, ""); LLVMBuildStore(b, v_off_start, v_offp); } @@ -337,7 +339,7 @@ LLVMBuildCondBr(b, LLVMBuildICmp(b, LLVMIntULT, v_maxatt, - l_int16_const(natts), + l_int16_const(lc, natts), ""), b_adjust_unavail_cols, b_find_start); @@ -346,8 +348,8 @@ LLVMPositionBuilderAtEnd(b, b_adjust_unavail_cols); v_params[0] = v_slot; - v_params[1] = LLVMBuildZExt(b, v_maxatt, LLVMInt32Type(), ""); - v_params[2] = l_int32_const(natts); + v_params[1] = LLVMBuildZExt(b, v_maxatt, LLVMInt32TypeInContext(lc), ""); + v_params[2] = l_int32_const(lc, natts); f = llvm_pg_func(mod, "slot_getmissingattrs"); l_call(b, LLVMGetFunctionType(f), f, @@ -357,7 +359,7 @@ LLVMPositionBuilderAtEnd(b, b_find_start); - v_nvalid = l_load(b, LLVMInt16Type(), v_nvalidp, ""); + v_nvalid = l_load(b, LLVMInt16TypeInContext(lc), v_nvalidp, ""); /* * Build switch to go from nvalid to the right startblock. Callers @@ -372,7 +374,7 @@ for (attnum = 0; attnum < natts; attnum++) { - LLVMValueRef v_attno = l_int16_const(attnum); + LLVMValueRef v_attno = l_int16_const(lc, attnum); LLVMAddCase(v_switch, v_attno, attcheckattnoblocks[attnum]); } @@ -396,7 +398,7 @@ Form_pg_attribute att = TupleDescAttr(desc, attnum); LLVMValueRef v_incby; int alignto; - LLVMValueRef l_attno = l_int16_const(attnum); + LLVMValueRef l_attno = l_int16_const(lc, attnum); LLVMValueRef v_attdatap; LLVMValueRef v_resultp; @@ -457,14 +459,14 @@ else b_next = attcheckattnoblocks[attnum + 1]; - v_nullbyteno = l_int32_const(attnum >> 3); - v_nullbytemask = l_int8_const(1 << ((attnum) & 0x07)); - v_nullbyte = l_load_gep1(b, LLVMInt8Type(), v_bits, v_nullbyteno, "attnullbyte"); + v_nullbyteno = l_int32_const(lc, attnum >> 3); + v_nullbytemask = l_int8_const(lc, 1 << ((attnum) & 0x07)); + v_nullbyte = l_load_gep1(b, LLVMInt8TypeInContext(lc), v_bits, v_nullbyteno, "attnullbyte"); v_nullbit = LLVMBuildICmp(b, LLVMIntEQ, LLVMBuildAnd(b, v_nullbyte, v_nullbytemask, ""), - l_int8_const(0), + l_int8_const(lc, 0), "attisnull"); v_attisnull = LLVMBuildAnd(b, v_hasnulls, v_nullbit, ""); @@ -475,8 +477,8 @@ /* store null-byte */ LLVMBuildStore(b, - l_int8_const(1), - l_gep(b, LLVMInt8Type(), v_tts_nulls, &l_attno, 1, "")); + l_int8_const(lc, 1), + l_gep(b, LLVMInt8TypeInContext(lc), v_tts_nulls, &l_attno, 1, "")); /* store zero datum */ LLVMBuildStore(b, l_sizet_const(0), @@ -542,10 +544,11 @@ v_off = l_load(b, TypeSizeT, v_offp, ""); v_possible_padbyte = - l_load_gep1(b, LLVMInt8Type(), v_tupdata_base, v_off, "padbyte"); + l_load_gep1(b, LLVMInt8TypeInContext(lc), v_tupdata_base, + v_off, "padbyte"); v_ispad = LLVMBuildICmp(b, LLVMIntEQ, - v_possible_padbyte, l_int8_const(0), + v_possible_padbyte, l_int8_const(lc, 0), "ispadbyte"); LLVMBuildCondBr(b, v_ispad, attalignblocks[attnum], @@ -653,14 +656,14 @@ LLVMValueRef v_off = l_load(b, TypeSizeT, v_offp, ""); v_attdatap = - l_gep(b, LLVMInt8Type(), v_tupdata_base, &v_off, 1, ""); + l_gep(b, LLVMInt8TypeInContext(lc), v_tupdata_base, &v_off, 1, ""); } /* compute address to store value at */ v_resultp = l_gep(b, TypeSizeT, v_tts_values, &l_attno, 1, ""); /* store null-byte (false) */ - LLVMBuildStore(b, l_int8_const(0), + LLVMBuildStore(b, l_int8_const(lc, 0), l_gep(b, TypeStorageBool, v_tts_nulls, &l_attno, 1, "")); /* @@ -670,7 +673,7 @@ if (att->attbyval) { LLVMValueRef v_tmp_loaddata; - LLVMTypeRef vartype = LLVMIntType(att->attlen * 8); + LLVMTypeRef vartype = LLVMIntTypeInContext(lc, att->attlen * 8); LLVMTypeRef vartypep = LLVMPointerType(vartype, 0); v_tmp_loaddata = @@ -762,11 +765,11 @@ LLVMValueRef v_off = l_load(b, TypeSizeT, v_offp, ""); LLVMValueRef v_flags; - LLVMBuildStore(b, l_int16_const(natts), v_nvalidp); - v_off = LLVMBuildTrunc(b, v_off, LLVMInt32Type(), ""); + LLVMBuildStore(b, l_int16_const(lc, natts), v_nvalidp); + v_off = LLVMBuildTrunc(b, v_off, LLVMInt32TypeInContext(lc), ""); LLVMBuildStore(b, v_off, v_slotoffp); - v_flags = l_load(b, LLVMInt16Type(), v_flagsp, "tts_flags"); - v_flags = LLVMBuildOr(b, v_flags, l_int16_const(TTS_FLAG_SLOW), ""); + v_flags = l_load(b, LLVMInt16TypeInContext(lc), v_flagsp, "tts_flags"); + v_flags = LLVMBuildOr(b, v_flags, l_int16_const(lc, TTS_FLAG_SLOW), ""); LLVMBuildStore(b, v_flags, v_flagsp); LLVMBuildRetVoid(b); } diff -Nru postgresql-13-13.13/src/backend/jit/llvm/llvmjit_expr.c postgresql-13-13.14/src/backend/jit/llvm/llvmjit_expr.c --- postgresql-13-13.13/src/backend/jit/llvm/llvmjit_expr.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/jit/llvm/llvmjit_expr.c 2024-02-05 21:47:02.000000000 +0000 @@ -84,6 +84,7 @@ LLVMBuilderRef b; LLVMModuleRef mod; + LLVMContextRef lc; LLVMValueRef eval_fn; LLVMBasicBlockRef entry; LLVMBasicBlockRef *opblocks; @@ -143,8 +144,9 @@ INSTR_TIME_SET_CURRENT(starttime); mod = llvm_mutable_module(context); + lc = LLVMGetModuleContext(mod); - b = LLVMCreateBuilder(); + b = LLVMCreateBuilderInContext(lc); funcname = llvm_expand_funcname(context, "evalexpr"); @@ -155,7 +157,7 @@ LLVMSetVisibility(eval_fn, LLVMDefaultVisibility); llvm_copy_attributes(AttributeTemplate, eval_fn); - entry = LLVMAppendBasicBlock(eval_fn, "entry"); + entry = LLVMAppendBasicBlockInContext(lc, eval_fn, "entry"); /* build state */ v_state = LLVMGetParam(eval_fn, 0); @@ -337,7 +339,7 @@ ""); LLVMBuildCondBr(b, LLVMBuildICmp(b, LLVMIntUGE, v_nvalid, - l_int16_const(op->d.fetch.last_var), + l_int16_const(lc, op->d.fetch.last_var), ""), opblocks[opno + 1], b_fetch); @@ -373,7 +375,7 @@ LLVMValueRef params[2]; params[0] = v_slot; - params[1] = l_int32_const(op->d.fetch.last_var); + params[1] = l_int32_const(lc, op->d.fetch.last_var); l_call(b, llvm_pg_var_func_type("slot_getsomeattrs_int"), @@ -411,7 +413,7 @@ v_nulls = v_scannulls; } - v_attnum = l_int32_const(op->d.var.attnum); + v_attnum = l_int32_const(lc, op->d.var.attnum); value = l_load_gep1(b, TypeSizeT, v_values, v_attnum, ""); isnull = l_load_gep1(b, TypeStorageBool, v_nulls, v_attnum, ""); LLVMBuildStore(b, value, v_resvaluep); @@ -477,12 +479,12 @@ } /* load data */ - v_attnum = l_int32_const(op->d.assign_var.attnum); + v_attnum = l_int32_const(lc, op->d.assign_var.attnum); v_value = l_load_gep1(b, TypeSizeT, v_values, v_attnum, ""); v_isnull = l_load_gep1(b, TypeStorageBool, v_nulls, v_attnum, ""); /* compute addresses of targets */ - v_resultnum = l_int32_const(op->d.assign_var.resultnum); + v_resultnum = l_int32_const(lc, op->d.assign_var.resultnum); v_rvaluep = l_gep(b, TypeSizeT, v_resultvalues, @@ -515,7 +517,7 @@ v_isnull = l_load(b, TypeStorageBool, v_tmpisnullp, ""); /* compute addresses of targets */ - v_resultnum = l_int32_const(resultnum); + v_resultnum = l_int32_const(lc, resultnum); v_rvaluep = l_gep(b, TypeSizeT, v_resultvalues, &v_resultnum, 1, ""); v_risnullp = @@ -1718,7 +1720,7 @@ v_cmpresult = LLVMBuildTrunc(b, l_load(b, TypeSizeT, v_resvaluep, ""), - LLVMInt32Type(), ""); + LLVMInt32TypeInContext(lc), ""); switch (rctype) { @@ -1744,7 +1746,7 @@ v_result = LLVMBuildICmp(b, predicate, v_cmpresult, - l_int32_const(0), + l_int32_const(lc, 0), ""); v_result = LLVMBuildZExt(b, v_result, TypeSizeT, ""); @@ -1898,8 +1900,8 @@ * load it from memory each time round. */ v_aggnop = l_ptr_const(&aggref->aggno, - l_ptr(LLVMInt32Type())); - v_aggno = l_load(b, LLVMInt32Type(), v_aggnop, "v_aggno"); + l_ptr(LLVMInt32TypeInContext(lc))); + v_aggno = l_load(b, LLVMInt32TypeInContext(lc), v_aggnop, "v_aggno"); /* load agg value / null */ value = l_load_gep1(b, TypeSizeT, v_aggvalues, v_aggno, "aggvalue"); @@ -1933,8 +1935,8 @@ * expression). So load it from memory each time round. */ v_wfuncnop = l_ptr_const(&wfunc->wfuncno, - l_ptr(LLVMInt32Type())); - v_wfuncno = l_load(b, LLVMInt32Type(), v_wfuncnop, "v_wfuncno"); + l_ptr(LLVMInt32TypeInContext(lc))); + v_wfuncno = l_load(b, LLVMInt32TypeInContext(lc), v_wfuncnop, "v_wfuncno"); /* load window func value / null */ value = l_load_gep1(b, TypeSizeT, v_aggvalues, v_wfuncno, @@ -2047,7 +2049,7 @@ /* strict function, check for NULL args */ for (int argno = 0; argno < nargs; argno++) { - LLVMValueRef v_argno = l_int32_const(argno); + LLVMValueRef v_argno = l_int32_const(lc, argno); LLVMValueRef v_argisnull; LLVMBasicBlockRef b_argnotnull; @@ -2106,7 +2108,7 @@ FIELDNO_AGGSTATE_ALL_PERGROUPS, "aggstate.all_pergroups"); - v_setoff = l_int32_const(op->d.agg_plain_pergroup_nullcheck.setoff); + v_setoff = l_int32_const(lc, op->d.agg_plain_pergroup_nullcheck.setoff); v_pergroup_allaggs = l_load_gep1(b, l_ptr(StructAggStatePerGroupData), v_allpergroupsp, v_setoff, ""); @@ -2178,8 +2180,8 @@ v_aggstatep, FIELDNO_AGGSTATE_ALL_PERGROUPS, "aggstate.all_pergroups"); - v_setoff = l_int32_const(op->d.agg_trans.setoff); - v_transno = l_int32_const(op->d.agg_trans.transno); + v_setoff = l_int32_const(lc, op->d.agg_trans.setoff); + v_transno = l_int32_const(lc, op->d.agg_trans.transno); v_pergroupp = l_gep(b, StructAggStatePerGroupData, @@ -2293,7 +2295,7 @@ /* set aggstate globals */ LLVMBuildStore(b, v_aggcontext, v_curaggcontext); - LLVMBuildStore(b, l_int32_const(op->d.agg_trans.setno), + LLVMBuildStore(b, l_int32_const(lc, op->d.agg_trans.setno), v_current_setp); LLVMBuildStore(b, v_pertransp, v_current_pertransp); @@ -2489,11 +2491,14 @@ LLVMModuleRef mod, FunctionCallInfo fcinfo, LLVMValueRef *v_fcinfo_isnull) { + LLVMContextRef lc; LLVMValueRef v_fn; LLVMValueRef v_fcinfo_isnullp; LLVMValueRef v_retval; LLVMValueRef v_fcinfo; + lc = LLVMGetModuleContext(mod); + v_fn = llvm_function_reference(context, b, mod, fcinfo); v_fcinfo = l_ptr_const(fcinfo, l_ptr(StructFunctionCallInfoData)); @@ -2517,12 +2522,12 @@ LLVMValueRef v_lifetime = create_LifetimeEnd(mod); LLVMValueRef params[2]; - params[0] = l_int64_const(sizeof(NullableDatum) * fcinfo->nargs); - params[1] = l_ptr_const(fcinfo->args, l_ptr(LLVMInt8Type())); + params[0] = l_int64_const(lc, sizeof(NullableDatum) * fcinfo->nargs); + params[1] = l_ptr_const(fcinfo->args, l_ptr(LLVMInt8TypeInContext(lc))); l_call(b, LLVMGetFunctionType(v_lifetime), v_lifetime, params, lengthof(params), ""); - params[0] = l_int64_const(sizeof(fcinfo->isnull)); - params[1] = l_ptr_const(&fcinfo->isnull, l_ptr(LLVMInt8Type())); + params[0] = l_int64_const(lc, sizeof(fcinfo->isnull)); + params[1] = l_ptr_const(&fcinfo->isnull, l_ptr(LLVMInt8TypeInContext(lc))); l_call(b, LLVMGetFunctionType(v_lifetime), v_lifetime, params, lengthof(params), ""); } @@ -2568,6 +2573,7 @@ LLVMTypeRef sig; LLVMValueRef fn; LLVMTypeRef param_types[2]; + LLVMContextRef lc; /* LLVM 5+ has a variadic pointer argument */ #if LLVM_VERSION_MAJOR < 5 @@ -2580,12 +2586,12 @@ if (fn) return fn; - param_types[0] = LLVMInt64Type(); - param_types[1] = l_ptr(LLVMInt8Type()); + lc = LLVMGetModuleContext(mod); + param_types[0] = LLVMInt64TypeInContext(lc); + param_types[1] = l_ptr(LLVMInt8TypeInContext(lc)); - sig = LLVMFunctionType(LLVMVoidType(), - param_types, lengthof(param_types), - false); + sig = LLVMFunctionType(LLVMVoidTypeInContext(lc), param_types, + lengthof(param_types), false); fn = LLVMAddFunction(mod, nm, sig); LLVMSetFunctionCallConv(fn, LLVMCCallConv); diff -Nru postgresql-13-13.13/src/backend/jit/llvm/llvmjit_inline.cpp postgresql-13-13.14/src/backend/jit/llvm/llvmjit_inline.cpp --- postgresql-13-13.13/src/backend/jit/llvm/llvmjit_inline.cpp 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/jit/llvm/llvmjit_inline.cpp 2024-02-05 21:47:02.000000000 +0000 @@ -114,12 +114,12 @@ llvm::ManagedStatic summary_cache; -static std::unique_ptr llvm_build_inline_plan(llvm::Module *mod); +static std::unique_ptr llvm_build_inline_plan(LLVMContextRef lc, llvm::Module *mod); static void llvm_execute_inline_plan(llvm::Module *mod, ImportMapTy *globalsToInline); -static llvm::Module* load_module_cached(llvm::StringRef modPath); -static std::unique_ptr load_module(llvm::StringRef Identifier); +static llvm::Module* load_module_cached(LLVMContextRef c, llvm::StringRef modPath); +static std::unique_ptr load_module(LLVMContextRef c, llvm::StringRef Identifier); static std::unique_ptr llvm_load_summary(llvm::StringRef path); @@ -153,15 +153,28 @@ #endif /* + * Reset inlining related state. This needs to be called before the currently + * used LLVMContextRef is disposed (and a new one create), otherwise we would + * have dangling references to deleted modules. + */ +void +llvm_inline_reset_caches(void) +{ + module_cache->clear(); + summary_cache->clear(); +} + +/* * Perform inlining of external function references in M based on a simple * cost based analysis. */ void llvm_inline(LLVMModuleRef M) { + LLVMContextRef lc = LLVMGetModuleContext(M); llvm::Module *mod = llvm::unwrap(M); - std::unique_ptr globalsToInline = llvm_build_inline_plan(mod); + std::unique_ptr globalsToInline = llvm_build_inline_plan(lc, mod); if (!globalsToInline) return; llvm_execute_inline_plan(mod, globalsToInline.get()); @@ -172,7 +185,7 @@ * mod. */ static std::unique_ptr -llvm_build_inline_plan(llvm::Module *mod) +llvm_build_inline_plan(LLVMContextRef lc, llvm::Module *mod) { std::unique_ptr globalsToInline(new ImportMapTy()); FunctionInlineStates functionStates; @@ -271,7 +284,7 @@ continue; } - defMod = load_module_cached(modPath); + defMod = load_module_cached(lc, modPath); if (defMod->materializeMetadata()) elog(FATAL, "failed to materialize metadata"); @@ -466,20 +479,20 @@ * the cache state would get corrupted. */ static llvm::Module* -load_module_cached(llvm::StringRef modPath) +load_module_cached(LLVMContextRef lc, llvm::StringRef modPath) { auto it = module_cache->find(modPath); if (it == module_cache->end()) { it = module_cache->insert( - std::make_pair(modPath, load_module(modPath))).first; + std::make_pair(modPath, load_module(lc, modPath))).first; } return it->second.get(); } static std::unique_ptr -load_module(llvm::StringRef Identifier) +load_module(LLVMContextRef lc, llvm::StringRef Identifier) { LLVMMemoryBufferRef buf; LLVMModuleRef mod; @@ -491,7 +504,7 @@ if (LLVMCreateMemoryBufferWithContentsOfFile(path, &buf, &msg)) elog(FATAL, "failed to open bitcode file \"%s\": %s", path, msg); - if (LLVMGetBitcodeModuleInContext2(LLVMGetGlobalContext(), buf, &mod)) + if (LLVMGetBitcodeModuleInContext2(lc, buf, &mod)) elog(FATAL, "failed to parse bitcode in file \"%s\"", path); /* @@ -808,7 +821,10 @@ add_module_to_inline_search_path(InlineSearchPath& searchpath, llvm::StringRef modpath) { /* only extension in libdir are candidates for inlining for now */ - if (!modpath.startswith("$libdir/")) +#if LLVM_VERSION_MAJOR < 16 +#define starts_with startswith +#endif + if (!modpath.starts_with("$libdir/")) return; /* if there's no match, attempt to load */ diff -Nru postgresql-13-13.13/src/backend/libpq/auth.c postgresql-13-13.14/src/backend/libpq/auth.c --- postgresql-13-13.13/src/backend/libpq/auth.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/libpq/auth.c 2024-02-05 21:47:02.000000000 +0000 @@ -815,16 +815,15 @@ if (shadow_pass) pfree(shadow_pass); - - /* - * If get_role_password() returned error, return error, even if the - * authentication succeeded. - */ - if (!shadow_pass) + else { + /* + * If get_role_password() returned error, authentication better not + * have succeeded. + */ Assert(auth_result != STATUS_OK); - return STATUS_ERROR; } + return auth_result; } diff -Nru postgresql-13-13.13/src/backend/libpq/be-secure-gssapi.c postgresql-13-13.14/src/backend/libpq/be-secure-gssapi.c --- postgresql-13-13.13/src/backend/libpq/be-secure-gssapi.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/libpq/be-secure-gssapi.c 2024-02-05 21:47:02.000000000 +0000 @@ -60,8 +60,8 @@ static int PqGSSSendLength; /* End of data available in PqGSSSendBuffer */ static int PqGSSSendNext; /* Next index to send a byte from * PqGSSSendBuffer */ -static int PqGSSSendConsumed; /* Number of *unencrypted* bytes consumed for - * current contents of PqGSSSendBuffer */ +static int PqGSSSendConsumed; /* Number of source bytes encrypted but not + * yet reported as sent */ static char *PqGSSRecvBuffer; /* Received, encrypted data */ static int PqGSSRecvLength; /* End of data available in PqGSSRecvBuffer */ @@ -83,8 +83,8 @@ * * On success, returns the number of data bytes consumed (possibly less than * len). On failure, returns -1 with errno set appropriately. For retryable - * errors, caller should call again (passing the same data) once the socket - * is ready. + * errors, caller should call again (passing the same or more data) once the + * socket is ready. * * Dealing with fatal errors here is a bit tricky: we can't invoke elog(FATAL) * since it would try to write to the client, probably resulting in infinite @@ -98,19 +98,25 @@ minor; gss_buffer_desc input, output; - size_t bytes_sent = 0; size_t bytes_to_encrypt; size_t bytes_encrypted; gss_ctx_id_t gctx = port->gss->ctx; /* - * When we get a failure, we must not tell the caller we have successfully - * transmitted everything, else it won't retry. Hence a "success" - * (positive) return value must only count source bytes corresponding to - * fully-transmitted encrypted packets. The amount of source data - * corresponding to the current partly-transmitted packet is remembered in + * When we get a retryable failure, we must not tell the caller we have + * successfully transmitted everything, else it won't retry. For + * simplicity, we claim we haven't transmitted anything until we have + * successfully transmitted all "len" bytes. Between calls, the amount of + * the current input data that's already been encrypted and placed into + * PqGSSSendBuffer (and perhaps transmitted) is remembered in * PqGSSSendConsumed. On a retry, the caller *must* be sending that data * again, so if it offers a len less than that, something is wrong. + * + * Note: it may seem attractive to report partial write completion once + * we've successfully sent any encrypted packets. However, that can cause + * problems for callers; notably, pqPutMsgEnd's heuristic to send only + * full 8K blocks interacts badly with such a hack. We won't save much, + * typically, by letting callers discard data early, so don't risk it. */ if (len < PqGSSSendConsumed) { @@ -118,6 +124,7 @@ errno = ECONNRESET; return -1; } + /* Discount whatever source data we already encrypted. */ bytes_to_encrypt = len - PqGSSSendConsumed; bytes_encrypted = PqGSSSendConsumed; @@ -146,33 +153,20 @@ ret = secure_raw_write(port, PqGSSSendBuffer + PqGSSSendNext, amount); if (ret <= 0) - { - /* - * Report any previously-sent data; if there was none, reflect - * the secure_raw_write result up to our caller. When there - * was some, we're effectively assuming that any interesting - * failure condition will recur on the next try. - */ - if (bytes_sent) - return bytes_sent; return ret; - } /* * Check if this was a partial write, and if so, move forward that * far in our buffer and try again. */ - if (ret != amount) + if (ret < amount) { PqGSSSendNext += ret; continue; } - /* We've successfully sent whatever data was in that packet. */ - bytes_sent += PqGSSSendConsumed; - - /* All encrypted data was sent, our buffer is empty now. */ - PqGSSSendLength = PqGSSSendNext = PqGSSSendConsumed = 0; + /* We've successfully sent whatever data was in the buffer. */ + PqGSSSendLength = PqGSSSendNext = 0; } /* @@ -196,7 +190,10 @@ output.value = NULL; output.length = 0; - /* Create the next encrypted packet */ + /* + * Create the next encrypted packet. Any failure here is considered a + * hard failure, so we return -1 even if some data has been sent. + */ major = gss_wrap(&minor, gctx, 1, GSS_C_QOP_DEFAULT, &input, &conf_state, &output); if (major != GSS_S_COMPLETE) @@ -239,10 +236,13 @@ } /* If we get here, our counters should all match up. */ - Assert(bytes_sent == len); - Assert(bytes_sent == bytes_encrypted); + Assert(len == PqGSSSendConsumed); + Assert(len == bytes_encrypted); + + /* We're reporting all the data as sent, so reset PqGSSSendConsumed. */ + PqGSSSendConsumed = 0; - return bytes_sent; + return bytes_encrypted; } /* diff -Nru postgresql-13-13.13/src/backend/libpq/be-secure-openssl.c postgresql-13-13.14/src/backend/libpq/be-secure-openssl.c --- postgresql-13-13.13/src/backend/libpq/be-secure-openssl.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/libpq/be-secure-openssl.c 2024-02-05 21:47:02.000000000 +0000 @@ -424,6 +424,7 @@ * per-thread error queue following another call to an OpenSSL I/O * routine. */ + errno = 0; ERR_clear_error(); r = SSL_accept(port->ssl); if (r <= 0) @@ -460,7 +461,7 @@ WAIT_EVENT_SSL_OPEN_SERVER); goto aloop; case SSL_ERROR_SYSCALL: - if (r < 0) + if (r < 0 && errno != 0) ereport(COMMERROR, (errcode_for_socket_access(), errmsg("could not accept SSL connection: %m"))); @@ -636,7 +637,7 @@ break; case SSL_ERROR_SYSCALL: /* leave it to caller to ereport the value of errno */ - if (n != -1) + if (n != -1 || errno == 0) { errno = ECONNRESET; n = -1; @@ -694,8 +695,14 @@ n = -1; break; case SSL_ERROR_SYSCALL: - /* leave it to caller to ereport the value of errno */ - if (n != -1) + + /* + * Leave it to caller to ereport the value of errno. However, if + * errno is still zero then assume it's a read EOF situation, and + * report ECONNRESET. (This seems possible because SSL_write can + * also do reads.) + */ + if (n != -1 || errno == 0) { errno = ECONNRESET; n = -1; @@ -748,11 +755,6 @@ * to retry; do we need to adopt their logic for that? */ -#ifndef HAVE_BIO_GET_DATA -#define BIO_get_data(bio) (bio->ptr) -#define BIO_set_data(bio, data) (bio->ptr = data) -#endif - static BIO_METHOD *my_bio_methods = NULL; static int @@ -762,7 +764,7 @@ if (buf != NULL) { - res = secure_raw_read(((Port *) BIO_get_data(h)), buf, size); + res = secure_raw_read(((Port *) BIO_get_app_data(h)), buf, size); BIO_clear_retry_flags(h); if (res <= 0) { @@ -782,7 +784,7 @@ { int res = 0; - res = secure_raw_write(((Port *) BIO_get_data(h)), buf, size); + res = secure_raw_write(((Port *) BIO_get_app_data(h)), buf, size); BIO_clear_retry_flags(h); if (res <= 0) { @@ -858,7 +860,7 @@ SSLerr(SSL_F_SSL_SET_FD, ERR_R_BUF_LIB); goto err; } - BIO_set_data(bio, port); + BIO_set_app_data(bio, port); BIO_set_fd(bio, fd, BIO_NOCLOSE); SSL_set_bio(port->ssl, bio, bio); diff -Nru postgresql-13-13.13/src/backend/libpq/pqcomm.c postgresql-13-13.14/src/backend/libpq/pqcomm.c --- postgresql-13-13.13/src/backend/libpq/pqcomm.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/libpq/pqcomm.c 2024-02-05 21:47:02.000000000 +0000 @@ -944,6 +944,8 @@ { int r; + errno = 0; + r = secure_read(MyProcPort, PqRecvBuffer + PqRecvLength, PQ_RECV_BUFFER_SIZE - PqRecvLength); @@ -956,10 +958,13 @@ * Careful: an ereport() that tries to write to the client would * cause recursion to here, leading to stack overflow and core * dump! This message must go *only* to the postmaster log. + * + * If errno is zero, assume it's EOF and let the caller complain. */ - ereport(COMMERROR, - (errcode_for_socket_access(), - errmsg("could not receive data from client: %m"))); + if (errno != 0) + ereport(COMMERROR, + (errcode_for_socket_access(), + errmsg("could not receive data from client: %m"))); return EOF; } if (r == 0) @@ -1036,6 +1041,8 @@ /* Put the socket into non-blocking mode */ socket_set_nonblocking(true); + errno = 0; + r = secure_read(MyProcPort, c, 1); if (r < 0) { @@ -1052,10 +1059,13 @@ * Careful: an ereport() that tries to write to the client would * cause recursion to here, leading to stack overflow and core * dump! This message must go *only* to the postmaster log. + * + * If errno is zero, assume it's EOF and let the caller complain. */ - ereport(COMMERROR, - (errcode_for_socket_access(), - errmsg("could not receive data from client: %m"))); + if (errno != 0) + ereport(COMMERROR, + (errcode_for_socket_access(), + errmsg("could not receive data from client: %m"))); r = EOF; } } diff -Nru postgresql-13-13.13/src/backend/optimizer/prep/prepjointree.c postgresql-13-13.14/src/backend/optimizer/prep/prepjointree.c --- postgresql-13-13.13/src/backend/optimizer/prep/prepjointree.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/optimizer/prep/prepjointree.c 2024-02-05 21:47:02.000000000 +0000 @@ -2365,8 +2365,13 @@ else if (newnode && IsA(newnode, PlaceHolderVar) && ((PlaceHolderVar *) newnode)->phlevelsup == 0) { - /* No need to wrap a PlaceHolderVar with another one, either */ - wrap = false; + /* The same rules apply for a PlaceHolderVar */ + if (rcon->target_rte->lateral && + !bms_is_subset(((PlaceHolderVar *) newnode)->phrels, + rcon->relids)) + wrap = true; + else + wrap = false; } else if (rcon->wrap_non_vars) { diff -Nru postgresql-13-13.13/src/backend/optimizer/util/clauses.c postgresql-13-13.14/src/backend/optimizer/util/clauses.c --- postgresql-13-13.13/src/backend/optimizer/util/clauses.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/optimizer/util/clauses.c 2024-02-05 21:47:02.000000000 +0000 @@ -641,6 +641,11 @@ * mistakenly think that something like "WHERE random() < 0.5" can be treated * as a constant qualification. * + * This will give the right answer only for clauses that have been put + * through expression preprocessing. Callers outside the planner typically + * should use contain_mutable_functions_after_planning() instead, for the + * reasons given there. + * * We will recursively look into Query nodes (i.e., SubLink sub-selects) * but not into SubPlans. See comments for contain_volatile_functions(). */ @@ -700,6 +705,34 @@ context); } +/* + * contain_mutable_functions_after_planning + * Test whether given expression contains mutable functions. + * + * This is a wrapper for contain_mutable_functions() that is safe to use from + * outside the planner. The difference is that it first runs the expression + * through expression_planner(). There are two key reasons why we need that: + * + * First, function default arguments will get inserted, which may affect + * volatility (consider "default now()"). + * + * Second, inline-able functions will get inlined, which may allow us to + * conclude that the function is really less volatile than it's marked. + * As an example, polymorphic functions must be marked with the most volatile + * behavior that they have for any input type, but once we inline the + * function we may be able to conclude that it's not so volatile for the + * particular input type we're dealing with. + */ +bool +contain_mutable_functions_after_planning(Expr *expr) +{ + /* We assume here that expression_planner() won't scribble on its input */ + expr = expression_planner(expr); + + /* Now we can search for non-immutable functions */ + return contain_mutable_functions((Node *) expr); +} + /***************************************************************************** * Check clauses for volatile functions @@ -713,6 +746,11 @@ * volatile function) is found. This test prevents, for example, * invalid conversions of volatile expressions into indexscan quals. * + * This will give the right answer only for clauses that have been put + * through expression preprocessing. Callers outside the planner typically + * should use contain_volatile_functions_after_planning() instead, for the + * reasons given there. + * * We will recursively look into Query nodes (i.e., SubLink sub-selects) * but not into SubPlans. This is a bit odd, but intentional. If we are * looking at a SubLink, we are probably deciding whether a query tree @@ -770,6 +808,34 @@ } /* + * contain_volatile_functions_after_planning + * Test whether given expression contains volatile functions. + * + * This is a wrapper for contain_volatile_functions() that is safe to use from + * outside the planner. The difference is that it first runs the expression + * through expression_planner(). There are two key reasons why we need that: + * + * First, function default arguments will get inserted, which may affect + * volatility (consider "default random()"). + * + * Second, inline-able functions will get inlined, which may allow us to + * conclude that the function is really less volatile than it's marked. + * As an example, polymorphic functions must be marked with the most volatile + * behavior that they have for any input type, but once we inline the + * function we may be able to conclude that it's not so volatile for the + * particular input type we're dealing with. + */ +bool +contain_volatile_functions_after_planning(Expr *expr) +{ + /* We assume here that expression_planner() won't scribble on its input */ + expr = expression_planner(expr); + + /* Now we can search for volatile functions */ + return contain_volatile_functions((Node *) expr); +} + +/* * Special purpose version of contain_volatile_functions() for use in COPY: * ignore nextval(), but treat all other functions normally. */ diff -Nru postgresql-13-13.13/src/backend/optimizer/util/pathnode.c postgresql-13-13.14/src/backend/optimizer/util/pathnode.c --- postgresql-13-13.13/src/backend/optimizer/util/pathnode.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/optimizer/util/pathnode.c 2024-02-05 21:47:02.000000000 +0000 @@ -26,6 +26,7 @@ #include "optimizer/optimizer.h" #include "optimizer/pathnode.h" #include "optimizer/paths.h" +#include "optimizer/placeholder.h" #include "optimizer/planmain.h" #include "optimizer/prep.h" #include "optimizer/restrictinfo.h" @@ -56,6 +57,10 @@ static List *reparameterize_pathlist_by_child(PlannerInfo *root, List *pathlist, RelOptInfo *child_rel); +static bool contain_references_to(PlannerInfo *root, Node *clause, + Relids relids); +static bool ris_contain_references_to(PlannerInfo *root, List *rinfos, + Relids relids); /***************************************************************************** @@ -3949,6 +3954,40 @@ switch (nodeTag(path)) { case T_Path: + + /* + * If the path's restriction clauses contain lateral references to + * the other relation, we can't reparameterize, because we must + * not change the RelOptInfo's contents here. (Doing so would + * break things if we end up using a non-partitionwise join.) + */ + if (ris_contain_references_to(root, + path->parent->baserestrictinfo, + child_rel->top_parent_relids)) + return NULL; + + /* + * If it's a SampleScan with tablesample parameters referencing + * the other relation, we can't reparameterize, because we must + * not change the RTE's contents here. (Doing so would break + * things if we end up using a non-partitionwise join.) + */ + if (path->pathtype == T_SampleScan) + { + Index scan_relid = path->parent->relid; + RangeTblEntry *rte; + + /* it should be a base rel with a tablesample clause... */ + Assert(scan_relid > 0); + rte = planner_rt_fetch(scan_relid, root); + Assert(rte->rtekind == RTE_RELATION); + Assert(rte->tablesample != NULL); + + if (contain_references_to(root, (Node *) rte->tablesample, + child_rel->top_parent_relids)) + return NULL; + } + FLAT_COPY_PATH(new_path, path, Path); break; @@ -3956,6 +3995,18 @@ { IndexPath *ipath; + /* + * If the path's restriction clauses contain lateral + * references to the other relation, we can't reparameterize, + * because we must not change the IndexOptInfo's contents + * here. (Doing so would break things if we end up using a + * non-partitionwise join.) + */ + if (ris_contain_references_to(root, + path->parent->baserestrictinfo, + child_rel->top_parent_relids)) + return NULL; + FLAT_COPY_PATH(ipath, path, IndexPath); ADJUST_CHILD_ATTRS(ipath->indexclauses); new_path = (Path *) ipath; @@ -3966,6 +4017,18 @@ { BitmapHeapPath *bhpath; + /* + * If the path's restriction clauses contain lateral + * references to the other relation, we can't reparameterize, + * because we must not change the RelOptInfo's contents here. + * (Doing so would break things if we end up using a + * non-partitionwise join.) + */ + if (ris_contain_references_to(root, + path->parent->baserestrictinfo, + child_rel->top_parent_relids)) + return NULL; + FLAT_COPY_PATH(bhpath, path, BitmapHeapPath); REPARAMETERIZE_CHILD_PATH(bhpath->bitmapqual); new_path = (Path *) bhpath; @@ -3997,6 +4060,18 @@ ForeignPath *fpath; ReparameterizeForeignPathByChild_function rfpc_func; + /* + * If the path's restriction clauses contain lateral + * references to the other relation, we can't reparameterize, + * because we must not change the RelOptInfo's contents here. + * (Doing so would break things if we end up using a + * non-partitionwise join.) + */ + if (ris_contain_references_to(root, + path->parent->baserestrictinfo, + child_rel->top_parent_relids)) + return NULL; + FLAT_COPY_PATH(fpath, path, ForeignPath); if (fpath->fdw_outerpath) REPARAMETERIZE_CHILD_PATH(fpath->fdw_outerpath); @@ -4015,6 +4090,18 @@ { CustomPath *cpath; + /* + * If the path's restriction clauses contain lateral + * references to the other relation, we can't reparameterize, + * because we must not change the RelOptInfo's contents here. + * (Doing so would break things if we end up using a + * non-partitionwise join.) + */ + if (ris_contain_references_to(root, + path->parent->baserestrictinfo, + child_rel->top_parent_relids)) + return NULL; + FLAT_COPY_PATH(cpath, path, CustomPath); REPARAMETERIZE_CHILD_PATH_LIST(cpath->custom_paths); if (cpath->methods && @@ -4180,3 +4267,91 @@ return result; } + +/* + * contain_references_to + * Detect whether any Vars or PlaceHolderVars in the given clause contain + * lateral references to the given 'relids'. + */ +static bool +contain_references_to(PlannerInfo *root, Node *clause, Relids relids) +{ + bool ret = false; + List *vars; + ListCell *lc; + + /* + * Examine all Vars and PlaceHolderVars used in the clause. + * + * By omitting the relevant flags, this also gives us a cheap sanity check + * that no aggregates or window functions appear in the clause. We don't + * expect any of those in scan-level restrictions or tablesamples. + */ + vars = pull_var_clause(clause, PVC_INCLUDE_PLACEHOLDERS); + foreach(lc, vars) + { + Node *node = (Node *) lfirst(lc); + + if (IsA(node, Var)) + { + Var *var = (Var *) node; + + if (bms_is_member(var->varno, relids)) + { + ret = true; + break; + } + } + else if (IsA(node, PlaceHolderVar)) + { + PlaceHolderVar *phv = (PlaceHolderVar *) node; + PlaceHolderInfo *phinfo = find_placeholder_info(root, phv, false); + + /* + * We should check both ph_eval_at (in case the PHV is to be + * computed at the other relation and then laterally referenced + * here) and ph_lateral (in case the PHV is to be evaluated here + * but contains lateral references to the other relation). The + * former case should not occur in baserestrictinfo clauses, but + * it can occur in tablesample clauses. + */ + if (bms_overlap(phinfo->ph_eval_at, relids) || + bms_overlap(phinfo->ph_lateral, relids)) + { + ret = true; + break; + } + } + else + Assert(false); + } + + list_free(vars); + + return ret; +} + +/* + * ris_contain_references_to + * Apply contain_references_to() to a list of RestrictInfos. + * + * We need extra code for this because pull_var_clause() can't descend + * through RestrictInfos. + */ +static bool +ris_contain_references_to(PlannerInfo *root, List *rinfos, Relids relids) +{ + ListCell *lc; + + foreach(lc, rinfos) + { + RestrictInfo *rinfo = lfirst_node(RestrictInfo, lc); + + /* Pseudoconstant clauses can't contain any Vars or PHVs */ + if (rinfo->pseudoconstant) + continue; + if (contain_references_to(root, (Node *) rinfo->clause, relids)) + return true; + } + return false; +} diff -Nru postgresql-13-13.13/src/backend/po/de.po postgresql-13-13.14/src/backend/po/de.po --- postgresql-13-13.13/src/backend/po/de.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/de.po 2024-02-05 21:47:02.000000000 +0000 @@ -25582,7 +25582,7 @@ msgstr "Erzwingt die Synchronisierung von Aktualisierungen auf Festplatte." #: utils/misc/guc.c:1186 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "Der Server verwendet den Systemaufruf fsync() an mehreren Stellen, um sicherzustellen, dass Datenänderungen physikalisch auf die Festplatte geschrieben werden. Das stellt sicher, dass der Datenbankcluster nach einem Betriebssystemabsturz oder Hardwarefehler in einem korrekten Zustand wiederhergestellt werden kann." #: utils/misc/guc.c:1197 diff -Nru postgresql-13-13.13/src/backend/po/es.po postgresql-13-13.14/src/backend/po/es.po --- postgresql-13-13.13/src/backend/po/es.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/es.po 2024-02-05 21:47:02.000000000 +0000 @@ -25069,7 +25069,7 @@ msgstr "Forzar la sincronización de escrituras a disco." #: utils/misc/guc.c:1186 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "El servidor usará la llamada a sistema fsync() en varios lugares para asegurarse que las actualizaciones son escritas físicamente a disco. Esto asegura que las bases de datos se recuperarán a un estado consistente después de una caída de hardware o sistema operativo." #: utils/misc/guc.c:1197 diff -Nru postgresql-13-13.13/src/backend/po/fr.po postgresql-13-13.14/src/backend/po/fr.po --- postgresql-13-13.13/src/backend/po/fr.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/fr.po 2024-02-05 21:47:02.000000000 +0000 @@ -25488,7 +25488,7 @@ msgstr "Force la synchronisation des mises à jour sur le disque." #: utils/misc/guc.c:1186 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "" "Le serveur utilisera l'appel système fsync() à différents endroits pour\n" "s'assurer que les mises à jour sont écrites physiquement sur le disque. Ceci\n" diff -Nru postgresql-13-13.13/src/backend/po/it.po postgresql-13-13.14/src/backend/po/it.po --- postgresql-13-13.13/src/backend/po/it.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/it.po 2024-02-05 21:47:02.000000000 +0000 @@ -23835,7 +23835,7 @@ msgstr "Forza la sincronizzazione degli aggiornamenti sul disco." #: utils/misc/guc.c:1044 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "Il server userà in diversi punti la chiamata di sistema fsync() per assicurarsi che gli aggiornamenti vengano scritti fisicamente sul disco. Questo assicura che un cluster di database possa essere recuperato in uno stato consistente dopo un crash di sistema o dell'hardware." #: utils/misc/guc.c:1055 diff -Nru postgresql-13-13.13/src/backend/po/ja.po postgresql-13-13.14/src/backend/po/ja.po --- postgresql-13-13.13/src/backend/po/ja.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/ja.po 2024-02-05 21:47:02.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-09-20 09:18+0900\n" -"PO-Revision-Date: 2023-09-20 09:31+0900\n" +"POT-Creation-Date: 2023-11-10 09:55+0900\n" +"PO-Revision-Date: 2023-11-10 15:48+0900\n" "Last-Translator: Kyotaro Horiguchi \n" "Language-Team: jpug-doc \n" "Language: ja\n" @@ -24,36 +24,36 @@ msgid "not recorded" msgstr "記録されていません" -#: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 commands/copy.c:3499 commands/extension.c:3462 utils/adt/genfile.c:125 +#: ../common/controldata_utils.c:78 ../common/controldata_utils.c:83 commands/copy.c:3499 commands/extension.c:3462 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: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 +#: ../common/controldata_utils.c:96 ../common/controldata_utils.c:99 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:3472 libpq/hba.c:499 replication/logical/origin.c:717 replication/logical/origin.c:753 replication/logical/reorderbuffer.c:3661 replication/logical/snapbuild.c:1874 replication/logical/snapbuild.c:1916 replication/logical/snapbuild.c:1944 replication/logical/snapbuild.c:1971 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" msgstr "ファイル\"%s\"の読み取りに失敗しました: %m" -#: ../common/controldata_utils.c:97 ../common/controldata_utils.c:101 access/transam/twophase.c:1337 access/transam/xlog.c:3533 access/transam/xlog.c:4777 replication/logical/origin.c:722 replication/logical/origin.c:761 replication/logical/snapbuild.c:1879 replication/logical/snapbuild.c:1921 replication/logical/snapbuild.c:1949 replication/logical/snapbuild.c:1976 replication/slot.c:1720 replication/slot.c:1761 replication/walsender.c:553 +#: ../common/controldata_utils.c:107 ../common/controldata_utils.c:111 access/transam/twophase.c:1337 access/transam/xlog.c:3533 access/transam/xlog.c:4777 replication/logical/origin.c:722 replication/logical/origin.c:761 replication/logical/snapbuild.c:1879 replication/logical/snapbuild.c:1921 replication/logical/snapbuild.c:1949 replication/logical/snapbuild.c:1976 replication/slot.c:1720 replication/slot.c:1761 replication/walsender.c:553 #: utils/cache/relmapper.c:748 #, c-format msgid "could not read file \"%s\": read %d of %zu" msgstr "ファイル\"%1$s\"を読み込めませんでした: %3$zuバイトのうち%2$dバイトを読み込みました" -#: ../common/controldata_utils.c:112 ../common/controldata_utils.c:117 ../common/controldata_utils.c:256 ../common/controldata_utils.c:259 access/heap/rewriteheap.c:1178 access/heap/rewriteheap.c:1281 access/transam/timeline.c:392 access/transam/timeline.c:438 access/transam/timeline.c:516 access/transam/twophase.c:1346 access/transam/twophase.c:1757 access/transam/xlog.c:3397 access/transam/xlog.c:3568 access/transam/xlog.c:3573 access/transam/xlog.c:3901 +#: ../common/controldata_utils.c:122 ../common/controldata_utils.c:127 ../common/controldata_utils.c:286 ../common/controldata_utils.c:289 access/heap/rewriteheap.c:1178 access/heap/rewriteheap.c:1281 access/transam/timeline.c:392 access/transam/timeline.c:438 access/transam/timeline.c:516 access/transam/twophase.c:1346 access/transam/twophase.c:1757 access/transam/xlog.c:3397 access/transam/xlog.c:3568 access/transam/xlog.c:3573 access/transam/xlog.c:3901 #: access/transam/xlog.c:4742 access/transam/xlog.c:5666 access/transam/xlogfuncs.c:687 commands/copy.c:1813 libpq/be-fsstubs.c:455 libpq/be-fsstubs.c:525 replication/logical/origin.c:655 replication/logical/origin.c:794 replication/logical/reorderbuffer.c:3719 replication/logical/snapbuild.c:1783 replication/logical/snapbuild.c:1984 replication/slot.c:1607 replication/slot.c:1768 replication/walsender.c:563 storage/file/copydir.c:218 storage/file/copydir.c:223 #: storage/file/fd.c:704 storage/file/fd.c:3445 storage/file/fd.c:3548 utils/cache/relmapper.c:759 utils/cache/relmapper.c:898 #, c-format msgid "could not close file \"%s\": %m" msgstr "ファイル\"%s\"をクローズできませんでした: %m" -#: ../common/controldata_utils.c:135 +#: ../common/controldata_utils.c:165 msgid "byte ordering mismatch" msgstr "バイトオーダが合っていません" -#: ../common/controldata_utils.c:137 +#: ../common/controldata_utils.c:167 #, c-format msgid "" "possible byte ordering mismatch\n" @@ -66,19 +66,19 @@ "されるものと一致しないようです。この場合以下の結果は不正確になります。また、\n" "PostgreSQLインストレーションはこのデータディレクトリと互換性がなくなります。" -#: ../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 +#: ../common/controldata_utils.c:227 ../common/controldata_utils.c:233 ../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:1738 replication/logical/snapbuild.c:1845 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 +#: 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:1329 utils/init/miscinit.c:1463 utils/init/miscinit.c:1540 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: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 +#: ../common/controldata_utils.c:251 ../common/controldata_utils.c:254 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:10663 access/transam/xlog.c:10690 +#: ../common/controldata_utils.c:269 ../common/controldata_utils.c:275 ../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:1776 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" @@ -468,32 +468,37 @@ msgid "request for BRIN range summarization for index \"%s\" page %u was not recorded" msgstr "インデックス\"%s\" ページ%uのBRIN範囲要約のリクエストは登録されていません" -#: 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 +#: access/brin/brin.c:962 access/brin/brin.c:1072 access/gin/ginfast.c:1042 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:963 access/brin/brin.c:1067 +#: access/brin/brin.c:963 access/brin/brin.c:1073 #, c-format msgid "BRIN control functions cannot be executed during recovery." msgstr "BRIN制御関数はリカバリ中は実行できません。" -#: access/brin/brin.c:971 access/brin/brin.c:1075 +#: access/brin/brin.c:971 access/brin/brin.c:1081 #, c-format msgid "block number out of range: %s" msgstr "ブロック番号が範囲外です: %s" -#: access/brin/brin.c:1015 access/brin/brin.c:1101 +#: access/brin/brin.c:1015 access/brin/brin.c:1107 #, c-format msgid "\"%s\" is not a BRIN index" msgstr "\"%s\"はBRINインデックスではありません" -#: access/brin/brin.c:1031 access/brin/brin.c:1117 +#: access/brin/brin.c:1031 access/brin/brin.c:1123 #, c-format msgid "could not open parent table of index %s" msgstr "インデックス%sの親テーブルをオープンできませんでした" -#: access/brin/brin_pageops.c:76 access/brin/brin_pageops.c:362 access/brin/brin_pageops.c:848 access/gin/ginentrypage.c:110 access/gist/gist.c:1438 access/spgist/spgdoinsert.c:1962 access/spgist/spgdoinsert.c:2230 +#: access/brin/brin.c:1040 access/brin/brin.c:1139 access/gin/ginfast.c:1087 parser/parse_utilcmd.c:2243 +#, c-format +msgid "index \"%s\" is not valid" +msgstr "インデックス\"%s\"は有効ではありません" + +#: access/brin/brin_pageops.c:76 access/brin/brin_pageops.c:362 access/brin/brin_pageops.c:848 access/gin/ginentrypage.c:110 access/gist/gist.c:1458 access/spgist/spgdoinsert.c:1962 access/spgist/spgdoinsert.c:2230 #, c-format msgid "index row size %zu exceeds maximum %zu for index \"%s\"" msgstr "インデックス行サイズ%1$zuはインデックス\"%3$s\"での最大値%2$zuを超えています" @@ -578,7 +583,7 @@ msgid "Attribute \"%s\" of type %s does not exist in type %s." msgstr "%2$s型の属性\"%1$s\"が%3$s型の中に存在しません。" -#: access/common/heaptuple.c:1124 access/common/heaptuple.c:1459 +#: access/common/heaptuple.c:1133 access/common/heaptuple.c:1468 #, c-format msgid "number of columns (%d) exceeds limit (%d)" msgstr "列数(%d)が上限(%d)を超えています" @@ -621,7 +626,7 @@ msgid "unrecognized parameter namespace \"%s\"" msgstr "認識できないパラメータ namaspace \"%s\"" -#: access/common/reloptions.c:1277 utils/misc/guc.c:12078 +#: access/common/reloptions.c:1277 utils/misc/guc.c:12086 #, c-format msgid "tables declared WITH OIDS are not supported" msgstr "WITH OIDSと定義されたテーブルはサポートされません" @@ -686,17 +691,17 @@ msgid "Reduce maintenance_work_mem." msgstr "maintenance_work_mem を小さくしてください。" -#: access/gin/ginfast.c:1044 +#: access/gin/ginfast.c:1043 #, c-format msgid "GIN pending list cannot be cleaned up during recovery." msgstr "GIN保留リストはリカバリ中には処理できません。" -#: access/gin/ginfast.c:1051 +#: access/gin/ginfast.c:1050 #, c-format msgid "\"%s\" is not a GIN index" msgstr "\"%s\"はGINインデックスではありません" -#: access/gin/ginfast.c:1062 +#: access/gin/ginfast.c:1061 #, c-format msgid "cannot access temporary indexes of other sessions" msgstr "他のセッションの一時インデックスにはアクセスできません" @@ -716,7 +721,7 @@ msgid "To fix this, do REINDEX INDEX \"%s\"." msgstr "これを修復するには REINDEX INDEX \"%s\" をおこなってください。" -#: access/gin/ginutil.c:144 executor/execExpr.c:1918 utils/adt/arrayfuncs.c:3790 utils/adt/arrayfuncs.c:6424 utils/adt/rowtypes.c:936 +#: access/gin/ginutil.c:144 executor/execExpr.c:1918 utils/adt/arrayfuncs.c:3839 utils/adt/arrayfuncs.c:6473 utils/adt/rowtypes.c:936 #, c-format msgid "could not identify a comparison function for type %s" msgstr "%s型の比較関数が見つかりません" @@ -781,7 +786,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: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 +#: 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:16452 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." @@ -889,7 +894,7 @@ msgstr "ファイル\"%s\"を%uバイトに切り詰められませんでした: %m" #: access/heap/rewriteheap.c:1159 access/transam/timeline.c:384 access/transam/timeline.c:424 access/transam/timeline.c:502 access/transam/xlog.c:3378 access/transam/xlog.c:3553 access/transam/xlog.c:4726 postmaster/postmaster.c:4663 postmaster/postmaster.c:4673 replication/logical/origin.c:587 replication/logical/origin.c:629 replication/logical/origin.c:648 replication/logical/snapbuild.c:1752 replication/slot.c:1575 storage/file/buffile.c:502 -#: storage/file/copydir.c:207 utils/init/miscinit.c:1396 utils/init/miscinit.c:1407 utils/init/miscinit.c:1415 utils/misc/guc.c:8036 utils/misc/guc.c:8067 utils/misc/guc.c:9997 utils/misc/guc.c:10011 utils/time/snapmgr.c:1363 utils/time/snapmgr.c:1370 +#: storage/file/copydir.c:207 utils/init/miscinit.c:1404 utils/init/miscinit.c:1415 utils/init/miscinit.c:1423 utils/misc/guc.c:8036 utils/misc/guc.c:8067 utils/misc/guc.c:10005 utils/misc/guc.c:10019 utils/time/snapmgr.c:1363 utils/time/snapmgr.c:1370 #, c-format msgid "could not write to file \"%s\": %m" msgstr "ファイル\"%s\"を書き出せませんでした: %m" @@ -1111,7 +1116,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:2664 commands/tablecmds.c:254 commands/tablecmds.c:278 commands/tablecmds.c:16142 commands/tablecmds.c:17646 +#: access/index/indexam.c:142 catalog/objectaddress.c:1260 commands/indexcmds.c:2664 commands/tablecmds.c:254 commands/tablecmds.c:278 commands/tablecmds.c:16150 commands/tablecmds.c:17654 #, c-format msgid "\"%s\" is not an index" msgstr "\"%s\"はインデックスではありません" @@ -1156,17 +1161,17 @@ msgid "This can be caused by an interrupted VACUUM in version 9.3 or older, before upgrade. Please REINDEX it." msgstr "これは9.3かそれ以前のバージョンで、アップグレード前にVACUUMが中断された際に起きた可能性があります。REINDEXしてください。" -#: access/nbtree/nbtutils.c:2664 +#: access/nbtree/nbtutils.c:2679 #, c-format msgid "index row size %zu exceeds btree version %u maximum %zu for index \"%s\"" msgstr "インデックス行サイズ%1$zuはインデックス\"%4$s\"でのbtreeバージョン %2$u の最大値%3$zuを超えています" -#: access/nbtree/nbtutils.c:2670 +#: access/nbtree/nbtutils.c:2685 #, c-format msgid "Index row references tuple (%u,%u) in relation \"%s\"." msgstr "インデックス行はリレーション\"%3$s\"のタプル(%1$u,%2$u)を参照しています。" -#: access/nbtree/nbtutils.c:2674 +#: access/nbtree/nbtutils.c:2689 #, c-format msgid "" "Values larger than 1/3 of a buffer page cannot be indexed.\n" @@ -1200,7 +1205,7 @@ msgid "\"%s\" is an index" msgstr "\"%s\"はインデックスです" -#: access/table/table.c:54 access/table/table.c:83 access/table/table.c:116 catalog/aclchk.c:1816 commands/tablecmds.c:12912 commands/tablecmds.c:16151 +#: access/table/table.c:54 access/table/table.c:83 access/table/table.c:116 catalog/aclchk.c:1816 commands/tablecmds.c:12912 commands/tablecmds.c:16159 #, c-format msgid "\"%s\" is a composite type" msgstr "\"%s\"は複合型です" @@ -1215,7 +1220,7 @@ msgid "%s cannot be empty." msgstr "%sは空にはできません。" -#: access/table/tableamapi.c:122 utils/misc/guc.c:12002 +#: access/table/tableamapi.c:122 utils/misc/guc.c:12010 #, c-format msgid "%s is too long (maximum %d characters)." msgstr "%s が長過ぎます（最大%d文字）。" @@ -1908,7 +1913,7 @@ msgid "could not generate secret authorization token" msgstr "秘密の認証トークンを生成できませんでした" -#: access/transam/xlog.c:4793 access/transam/xlog.c:4802 access/transam/xlog.c:4826 access/transam/xlog.c:4833 access/transam/xlog.c:4840 access/transam/xlog.c:4845 access/transam/xlog.c:4852 access/transam/xlog.c:4859 access/transam/xlog.c:4866 access/transam/xlog.c:4873 access/transam/xlog.c:4880 access/transam/xlog.c:4887 access/transam/xlog.c:4896 access/transam/xlog.c:4903 utils/init/miscinit.c:1553 +#: access/transam/xlog.c:4793 access/transam/xlog.c:4802 access/transam/xlog.c:4826 access/transam/xlog.c:4833 access/transam/xlog.c:4840 access/transam/xlog.c:4845 access/transam/xlog.c:4852 access/transam/xlog.c:4859 access/transam/xlog.c:4866 access/transam/xlog.c:4873 access/transam/xlog.c:4880 access/transam/xlog.c:4887 access/transam/xlog.c:4896 access/transam/xlog.c:4903 utils/init/miscinit.c:1561 #, c-format msgid "database files are incompatible with server" msgstr "データベースファイルがサーバと互換性がありません" @@ -2796,13 +2801,13 @@ msgstr "pg_stop_backup('f') を実行しようとしていたのではないですか?" #: access/transam/xlogfuncs.c:185 commands/event_trigger.c:1332 commands/event_trigger.c:1890 commands/extension.c:1965 commands/extension.c:2073 commands/extension.c:2358 commands/prepare.c:716 executor/execExpr.c:2259 executor/execSRF.c:728 executor/functions.c:1055 foreign/foreign.c:520 libpq/hba.c:2670 replication/logical/launcher.c:1086 replication/logical/logicalfuncs.c:157 replication/logical/origin.c:1486 replication/slotfuncs.c:252 -#: replication/walsender.c:3301 storage/ipc/shmem.c:550 utils/adt/datetime.c:4765 utils/adt/genfile.c:505 utils/adt/genfile.c:588 utils/adt/jsonfuncs.c:1792 utils/adt/jsonfuncs.c:1904 utils/adt/jsonfuncs.c:2092 utils/adt/jsonfuncs.c:2201 utils/adt/jsonfuncs.c:3663 utils/adt/misc.c:216 utils/adt/pgstatfuncs.c:476 utils/adt/pgstatfuncs.c:584 utils/adt/pgstatfuncs.c:1719 utils/fmgr/funcapi.c:72 utils/misc/guc.c:9698 utils/mmgr/portalmem.c:1145 +#: replication/walsender.c:3301 storage/ipc/shmem.c:550 utils/adt/datetime.c:4765 utils/adt/genfile.c:505 utils/adt/genfile.c:588 utils/adt/jsonfuncs.c:1792 utils/adt/jsonfuncs.c:1904 utils/adt/jsonfuncs.c:2092 utils/adt/jsonfuncs.c:2201 utils/adt/jsonfuncs.c:3663 utils/adt/misc.c:216 utils/adt/pgstatfuncs.c:476 utils/adt/pgstatfuncs.c:584 utils/adt/pgstatfuncs.c:1719 utils/fmgr/funcapi.c:72 utils/misc/guc.c:9705 utils/mmgr/portalmem.c:1145 #, c-format msgid "set-valued function called in context that cannot accept a set" msgstr "このコンテキストで集合値の関数は集合を受け付けられません" #: access/transam/xlogfuncs.c:189 commands/event_trigger.c:1336 commands/event_trigger.c:1894 commands/extension.c:1969 commands/extension.c:2077 commands/extension.c:2362 commands/prepare.c:720 foreign/foreign.c:525 libpq/hba.c:2674 replication/logical/launcher.c:1090 replication/logical/logicalfuncs.c:161 replication/logical/origin.c:1490 replication/slotfuncs.c:256 replication/walsender.c:3305 storage/ipc/shmem.c:554 utils/adt/datetime.c:4769 -#: utils/adt/genfile.c:509 utils/adt/genfile.c:592 utils/adt/misc.c:220 utils/adt/pgstatfuncs.c:480 utils/adt/pgstatfuncs.c:588 utils/adt/pgstatfuncs.c:1723 utils/misc/guc.c:9702 utils/misc/pg_config.c:43 utils/mmgr/portalmem.c:1149 +#: utils/adt/genfile.c:509 utils/adt/genfile.c:592 utils/adt/misc.c:220 utils/adt/pgstatfuncs.c:480 utils/adt/pgstatfuncs.c:588 utils/adt/pgstatfuncs.c:1723 utils/misc/guc.c:9709 utils/misc/pg_config.c:43 utils/mmgr/portalmem.c:1149 #, c-format msgid "materialize mode required, but it is not allowed in this context" msgstr "マテリアライズモードが必要ですが、現在のコンテクストで禁止されています" @@ -2857,7 +2862,7 @@ msgid "\"wait_seconds\" must not be negative or zero" msgstr "\"wait_seconds\"は負の値もしくはゼロにはできません" -#: access/transam/xlogfuncs.c:748 storage/ipc/signalfuncs.c:164 +#: access/transam/xlogfuncs.c:748 storage/ipc/signalfuncs.c:169 #, c-format msgid "failed to send signal to postmaster: %m" msgstr "postmasterにシグナルを送信できませんでした: %m" @@ -2867,137 +2872,132 @@ msgid "server did not promote within %d seconds" msgstr "サーバは%d 秒以内に昇格しませんでした" -#: access/transam/xlogreader.c:354 +#: access/transam/xlogreader.c:323 #, c-format msgid "invalid record offset at %X/%X" msgstr "%X/%Xのレコードオフセットが不正です" -#: access/transam/xlogreader.c:362 +#: access/transam/xlogreader.c:331 #, c-format msgid "contrecord is requested by %X/%X" msgstr "%X/%Xでは継続レコードが必要です" -#: access/transam/xlogreader.c:403 access/transam/xlogreader.c:733 +#: access/transam/xlogreader.c:372 access/transam/xlogreader.c:719 #, c-format msgid "invalid record length at %X/%X: wanted %u, got %u" msgstr "%X/%Xのレコード長が不正です:長さは%uである必要がありますが、実際は%uでした" -#: access/transam/xlogreader.c:429 -#, c-format -msgid "record length %u at %X/%X too long" -msgstr "%2$X/%3$Xのレコード長%1$uが大きすぎます" - -#: access/transam/xlogreader.c:478 +#: access/transam/xlogreader.c:442 #, c-format msgid "there is no contrecord flag at %X/%X" msgstr "%X/%Xでcontrecordフラグがありません" -#: access/transam/xlogreader.c:491 +#: access/transam/xlogreader.c:455 #, c-format msgid "invalid contrecord length %u at %X/%X" msgstr "%2$X/%3$Xのcontrecordの長さ %1$u は不正です" -#: access/transam/xlogreader.c:741 +#: access/transam/xlogreader.c:727 #, c-format msgid "invalid resource manager ID %u at %X/%X" msgstr "%2$X/%3$XのリソースマネージャID %1$uは不正です" -#: access/transam/xlogreader.c:755 access/transam/xlogreader.c:772 +#: access/transam/xlogreader.c:741 access/transam/xlogreader.c:758 #, c-format msgid "record with incorrect prev-link %X/%X at %X/%X" msgstr "%3$X/%4$Xのレコードの後方リンク%1$X/%2$Xが不正です" -#: access/transam/xlogreader.c:809 +#: access/transam/xlogreader.c:797 #, c-format msgid "incorrect resource manager data checksum in record at %X/%X" msgstr "%X/%Xのレコード内のリソースマネージャデータのチェックサムが不正です" -#: access/transam/xlogreader.c:846 +#: access/transam/xlogreader.c:834 #, c-format msgid "invalid magic number %04X in log segment %s, offset %u" msgstr "ログセグメント%2$s、オフセット%3$uのマジックナンバー%1$04Xは不正です" -#: access/transam/xlogreader.c:860 access/transam/xlogreader.c:901 +#: access/transam/xlogreader.c:848 access/transam/xlogreader.c:889 #, c-format msgid "invalid info bits %04X in log segment %s, offset %u" msgstr "ログセグメント %2$s、オフセット%3$uの情報ビット%1$04Xは不正です" -#: access/transam/xlogreader.c:875 +#: access/transam/xlogreader.c:863 #, c-format msgid "WAL file is from different database system: WAL file database system identifier is %llu, pg_control database system identifier is %llu" msgstr "WALファイルは異なるデータベースシステム由来のものです: WALファイルのデータベースシステム識別子は %lluで、pg_control におけるデータベースシステム識別子は %lluです" -#: access/transam/xlogreader.c:883 +#: access/transam/xlogreader.c:871 #, c-format msgid "WAL file is from different database system: incorrect segment size in page header" msgstr "WAL ファイルは異なるデータベースシステム由来のものです: ページヘッダーのセグメントサイズが正しくありません" -#: access/transam/xlogreader.c:889 +#: access/transam/xlogreader.c:877 #, c-format msgid "WAL file is from different database system: incorrect XLOG_BLCKSZ in page header" msgstr "WAL ファイルは異なるデータベースシステム由来のものです: ページヘッダーのXLOG_BLCKSZが正しくありません" -#: access/transam/xlogreader.c:920 +#: access/transam/xlogreader.c:908 #, c-format msgid "unexpected pageaddr %X/%X in log segment %s, offset %u" msgstr "ログセグメント%3$s、オフセット%4$uに想定外のページアドレス%1$X/%2$X" -#: access/transam/xlogreader.c:945 +#: access/transam/xlogreader.c:933 #, c-format msgid "out-of-sequence timeline ID %u (after %u) in log segment %s, offset %u" msgstr "ログセグメント%3$s、オフセット%4$uのタイムラインID %1$u(%2$uの後)が順序通りではありません" -#: access/transam/xlogreader.c:1285 +#: access/transam/xlogreader.c:1273 #, c-format msgid "out-of-order block_id %u at %X/%X" msgstr "block_id %uが%X/%Xで不正です" -#: access/transam/xlogreader.c:1308 +#: access/transam/xlogreader.c:1296 #, c-format msgid "BKPBLOCK_HAS_DATA set, but no data included at %X/%X" msgstr "BKPBLOCK_HAS_DATAが設定されていますが、%X/%Xにデータがありません" -#: access/transam/xlogreader.c:1315 +#: access/transam/xlogreader.c:1303 #, c-format msgid "BKPBLOCK_HAS_DATA not set, but data length is %u at %X/%X" msgstr "BKPBLOCK_HAS_DATAが設定されていませんが、%2$X/%3$Xのデータ長は%1$uです" -#: access/transam/xlogreader.c:1351 +#: access/transam/xlogreader.c:1339 #, c-format msgid "BKPIMAGE_HAS_HOLE set, but hole offset %u length %u block image length %u at %X/%X" msgstr "BKPIMAGE_HAS_HOLEが設定されていますが、%4$X/%5$Xでホールオフセット%1$u、長さ%2$u、ブロックイメージ長%3$uです" -#: access/transam/xlogreader.c:1367 +#: access/transam/xlogreader.c:1355 #, c-format msgid "BKPIMAGE_HAS_HOLE not set, but hole offset %u length %u at %X/%X" msgstr "BKPIMAGE_HAS_HOLEが設定されていませんが、%3$X/%4$Xにおけるホールオフセット%1$uの長さが%2$uです" -#: access/transam/xlogreader.c:1382 +#: access/transam/xlogreader.c:1370 #, c-format msgid "BKPIMAGE_IS_COMPRESSED set, but block image length %u at %X/%X" msgstr "BKPIMAGE_IS_COMPRESSEDが設定されていますが、%2$X/%3$Xにおいてブロックイメージ長が%1$uです" -#: access/transam/xlogreader.c:1397 +#: access/transam/xlogreader.c:1385 #, c-format msgid "neither BKPIMAGE_HAS_HOLE nor BKPIMAGE_IS_COMPRESSED set, but block image length is %u at %X/%X" msgstr "BKPIMAGE_HAS_HOLEもBKPIMAGE_IS_COMPRESSEDも設定されていませんが、%2$X/%3$Xにおいてブロックイメージ長が%1$uです" -#: access/transam/xlogreader.c:1413 +#: access/transam/xlogreader.c:1401 #, c-format msgid "BKPBLOCK_SAME_REL set but no previous rel at %X/%X" msgstr "BKPBLOCK_SAME_RELが設定されていますが、%X/%Xにおいて以前のリレーションがありません" -#: access/transam/xlogreader.c:1425 +#: access/transam/xlogreader.c:1413 #, c-format msgid "invalid block_id %u at %X/%X" msgstr "%2$X/%3$Xにおけるblock_id %1$uが不正です" -#: access/transam/xlogreader.c:1514 +#: access/transam/xlogreader.c:1502 #, c-format msgid "record with invalid length at %X/%X" msgstr "%X/%Xのレコードのサイズが不正です" -#: access/transam/xlogreader.c:1603 +#: access/transam/xlogreader.c:1591 #, c-format msgid "invalid compressed image at %X/%X, block %d" msgstr "%X/%X、ブロック %d での圧縮イメージが不正です" @@ -3178,7 +3178,7 @@ msgid "column \"%s\" of relation \"%s\" does not exist" msgstr "リレーション\"%2$s\"の列\"%1$s\"は存在しません" -#: catalog/aclchk.c:1824 catalog/objectaddress.c:1267 commands/sequence.c:1148 commands/tablecmds.c:236 commands/tablecmds.c:16115 utils/adt/acl.c:2059 utils/adt/acl.c:2089 utils/adt/acl.c:2121 utils/adt/acl.c:2153 utils/adt/acl.c:2181 utils/adt/acl.c:2211 +#: catalog/aclchk.c:1824 catalog/objectaddress.c:1267 commands/sequence.c:1148 commands/tablecmds.c:236 commands/tablecmds.c:16123 utils/adt/acl.c:2059 utils/adt/acl.c:2089 utils/adt/acl.c:2121 utils/adt/acl.c:2153 utils/adt/acl.c:2181 utils/adt/acl.c:2211 #, c-format msgid "\"%s\" is not a sequence" msgstr "\"%s\"はシーケンスではありません" @@ -3748,8 +3748,8 @@ 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: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 +#: 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:1364 utils/misc/guc.c:6783 utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11012 utils/misc/guc.c:11046 utils/misc/guc.c:11080 utils/misc/guc.c:11123 +#: utils/misc/guc.c:11165 #, c-format msgid "%s" msgstr "%s" @@ -4004,39 +4004,39 @@ msgid "DROP INDEX CONCURRENTLY must be first action in transaction" msgstr "DROP INDEX CONCURRENTLYはトランザクション内で最初の操作でなければなりません" -#: catalog/index.c:2958 +#: catalog/index.c:2967 #, c-format msgid "building index \"%s\" on table \"%s\" serially" msgstr "テーブル\"%2$s\"のインデックス\"%1$s\"を非並列で構築しています" -#: catalog/index.c:2963 +#: catalog/index.c:2972 #, 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:3597 +#: catalog/index.c:3606 #, c-format msgid "cannot reindex temporary tables of other sessions" msgstr "他のセッションの一時テーブルはインデクス再構築できません" -#: catalog/index.c:3608 commands/indexcmds.c:3151 +#: catalog/index.c:3617 commands/indexcmds.c:3151 #, c-format msgid "cannot reindex invalid index on TOAST table" msgstr "TOASTテーブルの無効なインデックスの再作成はできません" -#: catalog/index.c:3730 +#: catalog/index.c:3739 #, c-format msgid "index \"%s\" was reindexed" msgstr "インデックス\"%s\"のインデックス再構築が完了しました" -#: catalog/index.c:3812 commands/indexcmds.c:3172 +#: catalog/index.c:3821 commands/indexcmds.c:3172 #, c-format msgid "REINDEX of partitioned tables is not yet implemented, skipping \"%s\"" msgstr "パーティションテーブルの REINDEX は実装されていません、\"%s\"はスキップします" -#: catalog/index.c:3867 +#: catalog/index.c:3876 #, c-format msgid "cannot reindex invalid index \"%s.%s\" on TOAST table, skipping" msgstr "TOASTテーブルの無効なインデックス \"%s.%s\"の再作成はできません、スキップします " @@ -4171,7 +4171,7 @@ msgid "cannot create temporary tables during a parallel operation" msgstr "並行処理中は一時テーブルを作成できません" -#: catalog/namespace.c:4293 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:11197 utils/misc/guc.c:11275 #, c-format msgid "List syntax is invalid." msgstr "リスト文法が無効です" @@ -4181,17 +4181,17 @@ msgid "\"%s\" is not a table" msgstr "\"%s\"はテーブルではありません" -#: catalog/objectaddress.c:1282 commands/tablecmds.c:242 commands/tablecmds.c:5787 commands/tablecmds.c:16120 commands/view.c:119 +#: catalog/objectaddress.c:1282 commands/tablecmds.c:242 commands/tablecmds.c:5787 commands/tablecmds.c:16128 commands/view.c:119 #, c-format msgid "\"%s\" is not a view" msgstr "\"%s\"はビューではありません" -#: catalog/objectaddress.c:1289 commands/matview.c:186 commands/tablecmds.c:248 commands/tablecmds.c:16125 +#: catalog/objectaddress.c:1289 commands/matview.c:186 commands/tablecmds.c:248 commands/tablecmds.c:16133 #, c-format msgid "\"%s\" is not a materialized view" msgstr "\"%s\"は実体化ビューではありません" -#: catalog/objectaddress.c:1296 commands/tablecmds.c:266 commands/tablecmds.c:5790 commands/tablecmds.c:16130 +#: catalog/objectaddress.c:1296 commands/tablecmds.c:266 commands/tablecmds.c:5790 commands/tablecmds.c:16138 #, c-format msgid "\"%s\" is not a foreign table" msgstr "\"%s\"は外部テーブルではありません" @@ -5168,7 +5168,7 @@ msgid "invalid page in block %u of relation %s" msgstr "リレーション%2$sのブロック%1$uに不正なページ" -#: catalog/toasting.c:112 commands/indexcmds.c:664 commands/tablecmds.c:5760 commands/tablecmds.c:15985 +#: catalog/toasting.c:112 commands/indexcmds.c:664 commands/tablecmds.c:5760 commands/tablecmds.c:15993 #, c-format msgid "\"%s\" is not a table or materialized view" msgstr "\"%s\"はテーブルや実体化ビューではありません" @@ -7560,7 +7560,7 @@ msgid "could not determine which collation to use for index expression" msgstr "インデックス式で使用する照合順序を特定できませんでした" -#: 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 +#: commands/indexcmds.c:1942 commands/tablecmds.c:16459 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 型では照合順序はサポートされません" @@ -7595,7 +7595,7 @@ msgid "access method \"%s\" does not support NULLS FIRST/LAST options" msgstr "アクセスメソッド\"%s\"はNULLS FIRST/LASTオプションをサポートしません" -#: commands/indexcmds.c:2124 commands/tablecmds.c:16476 commands/tablecmds.c:16482 commands/typecmds.c:1947 +#: commands/indexcmds.c:2124 commands/tablecmds.c:16484 commands/tablecmds.c:16490 commands/typecmds.c:1947 #, c-format msgid "data type %s has no default operator class for access method \"%s\"" msgstr "アクセスメソッド\"%2$s\"にはデータ型%1$s用のデフォルトの演算子クラスがありません" @@ -7970,7 +7970,7 @@ msgid "operator attribute \"%s\" cannot be changed" msgstr "演算子の属性\"%s\"は変更できません" -#: commands/policy.c:89 commands/policy.c:382 commands/statscmds.c:143 commands/tablecmds.c:1540 commands/tablecmds.c:2023 commands/tablecmds.c:3105 commands/tablecmds.c:5730 commands/tablecmds.c:8596 commands/tablecmds.c:16041 commands/tablecmds.c:16076 commands/trigger.c:309 commands/trigger.c:1214 commands/trigger.c:1323 rewrite/rewriteDefine.c:278 rewrite/rewriteDefine.c:956 rewrite/rewriteRemove.c:80 +#: commands/policy.c:89 commands/policy.c:382 commands/statscmds.c:143 commands/tablecmds.c:1540 commands/tablecmds.c:2023 commands/tablecmds.c:3105 commands/tablecmds.c:5730 commands/tablecmds.c:8596 commands/tablecmds.c:16049 commands/tablecmds.c:16084 commands/trigger.c:309 commands/trigger.c:1214 commands/trigger.c:1323 rewrite/rewriteDefine.c:278 rewrite/rewriteDefine.c:956 rewrite/rewriteRemove.c:80 #, c-format msgid "permission denied: \"%s\" is a system catalog" msgstr "権限がありません: \"%s\"はシステムカタログです" @@ -8536,7 +8536,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:17689 parser/parse_utilcmd.c:2217 +#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17697 parser/parse_utilcmd.c:2217 #, c-format msgid "index \"%s\" does not exist" msgstr "インデックス\"%s\"は存在しません" @@ -9476,7 +9476,7 @@ msgid "cannot change owner of sequence \"%s\"" msgstr "シーケンス\"%s\"の所有者を変更できません" -#: commands/tablecmds.c:12914 commands/tablecmds.c:16152 +#: commands/tablecmds.c:12914 commands/tablecmds.c:16160 #, c-format msgid "Use ALTER TYPE instead." msgstr "代わりにALTER TYPEを使用してください。" @@ -9556,12 +9556,12 @@ msgid "cannot inherit from a partition" msgstr "パーティションからの継承はできません" -#: commands/tablecmds.c:14031 commands/tablecmds.c:16792 +#: commands/tablecmds.c:14031 commands/tablecmds.c:16800 #, c-format msgid "circular inheritance not allowed" msgstr "循環継承を行うことはできません" -#: commands/tablecmds.c:14032 commands/tablecmds.c:16793 +#: commands/tablecmds.c:14032 commands/tablecmds.c:16801 #, c-format msgid "\"%s\" is already a child of \"%s\"." msgstr "\"%s\"はすでに\"%s\"の子です" @@ -9721,182 +9721,182 @@ msgid "relation \"%s\" already exists in schema \"%s\"" msgstr "リレーション\"%s\"はスキーマ\"%s\"内にすでに存在します" -#: commands/tablecmds.c:16135 +#: commands/tablecmds.c:16143 #, c-format msgid "\"%s\" is not a composite type" msgstr "\"%s\"は複合型ではありません" -#: commands/tablecmds.c:16167 +#: commands/tablecmds.c:16175 #, c-format msgid "\"%s\" is not a table, view, materialized view, sequence, or foreign table" msgstr "\"%s\"はテーブル、ビュー、実体化ビュー、シーケンス、外部テーブルではありません" -#: commands/tablecmds.c:16202 +#: commands/tablecmds.c:16210 #, c-format msgid "unrecognized partitioning strategy \"%s\"" msgstr "識別できないパーティションストラテジ \"%s\"" -#: commands/tablecmds.c:16210 +#: commands/tablecmds.c:16218 #, c-format msgid "cannot use \"list\" partition strategy with more than one column" msgstr "\"list\"パーティションストラテジは2つ以上の列に対しては使えません" -#: commands/tablecmds.c:16276 +#: commands/tablecmds.c:16284 #, c-format msgid "column \"%s\" named in partition key does not exist" msgstr "パーティションキーに指定されている列\"%s\"は存在しません" -#: commands/tablecmds.c:16284 +#: commands/tablecmds.c:16292 #, c-format msgid "cannot use system column \"%s\" in partition key" msgstr "パーティションキーでシステム列\"%s\"は使用できません" -#: commands/tablecmds.c:16295 commands/tablecmds.c:16409 +#: commands/tablecmds.c:16303 commands/tablecmds.c:16417 #, c-format msgid "cannot use generated column in partition key" msgstr "パーティションキーで生成カラムは使用できません" -#: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 rewrite/rewriteHandler.c:875 rewrite/rewriteHandler.c:892 +#: commands/tablecmds.c:16304 commands/tablecmds.c:16418 commands/trigger.c:649 rewrite/rewriteHandler.c:875 rewrite/rewriteHandler.c:892 #, c-format msgid "Column \"%s\" is a generated column." msgstr "列\"%s\"は生成カラムです。" -#: commands/tablecmds.c:16372 +#: commands/tablecmds.c:16380 #, c-format msgid "functions in partition key expression must be marked IMMUTABLE" msgstr "パーティションキー式で使われる関数はIMMUTABLE指定されている必要があります" -#: commands/tablecmds.c:16392 +#: commands/tablecmds.c:16400 #, c-format msgid "partition key expressions cannot contain system column references" msgstr "パーティションキー式はシステム列への参照を含むことができません" -#: commands/tablecmds.c:16422 +#: commands/tablecmds.c:16430 #, c-format msgid "cannot use constant expression as partition key" msgstr "定数式をパーティションキーとして使うことはできません" -#: commands/tablecmds.c:16443 +#: commands/tablecmds.c:16451 #, c-format msgid "could not determine which collation to use for partition expression" msgstr "パーティション式で使用する照合順序を特定できませんでした" -#: commands/tablecmds.c:16478 +#: commands/tablecmds.c:16486 #, c-format msgid "You must specify a hash operator class or define a default hash operator class for the data type." msgstr "ハッシュ演算子クラスを指定するか、もしくはこのデータ型にデフォルトのハッシュ演算子クラスを定義する必要があります。" -#: commands/tablecmds.c:16484 +#: commands/tablecmds.c:16492 #, c-format msgid "You must specify a btree operator class or define a default btree operator class for the data type." msgstr "btree演算子クラスを指定するか、もしくはこのデータ型にデフォルトのbtree演算子クラスを定義するかする必要があります。" -#: commands/tablecmds.c:16629 +#: commands/tablecmds.c:16637 #, c-format msgid "partition constraint for table \"%s\" is implied by existing constraints" msgstr "テーブル\"%s\"のパーティション制約は既存の制約によって暗黙的に満たされています" -#: commands/tablecmds.c:16633 partitioning/partbounds.c:3119 partitioning/partbounds.c:3170 +#: commands/tablecmds.c:16641 partitioning/partbounds.c:3119 partitioning/partbounds.c:3170 #, c-format msgid "updated partition constraint for default partition \"%s\" is implied by existing constraints" msgstr "デフォルトパーティション \"%s\" に対する更新されたパーティション制約は既存の制約によって暗黙的に満たされています" -#: commands/tablecmds.c:16732 +#: commands/tablecmds.c:16740 #, c-format msgid "\"%s\" is already a partition" msgstr "\"%s\"はすでパーティションです" -#: commands/tablecmds.c:16738 +#: commands/tablecmds.c:16746 #, c-format msgid "cannot attach a typed table as partition" msgstr "型付けされたテーブルをパーティションにアタッチすることはできません" -#: commands/tablecmds.c:16754 +#: commands/tablecmds.c:16762 #, c-format msgid "cannot attach inheritance child as partition" msgstr "継承子テーブルをパーティションにアタッチすることはできません" -#: commands/tablecmds.c:16768 +#: commands/tablecmds.c:16776 #, c-format msgid "cannot attach inheritance parent as partition" msgstr "継承親テーブルをパーティションにアタッチすることはできません" -#: commands/tablecmds.c:16802 +#: commands/tablecmds.c:16810 #, c-format msgid "cannot attach a temporary relation as partition of permanent relation \"%s\"" msgstr "一時リレーションを永続リレーション \"%s\" の子テーブルとしてアタッチすることはできません" -#: commands/tablecmds.c:16810 +#: commands/tablecmds.c:16818 #, c-format msgid "cannot attach a permanent relation as partition of temporary relation \"%s\"" msgstr "永続リレーションを一時リレーション\"%s\"のパーティション子テーブルとしてアタッチすることはできません" -#: commands/tablecmds.c:16818 +#: commands/tablecmds.c:16826 #, c-format msgid "cannot attach as partition of temporary relation of another session" msgstr "他セッションの一時リレーションのパーティション子テーブルとしてアタッチすることはできません" -#: commands/tablecmds.c:16825 +#: commands/tablecmds.c:16833 #, c-format msgid "cannot attach temporary relation of another session as partition" msgstr "他セッションの一時リレーションにパーティション子テーブルとしてアタッチすることはできません" -#: commands/tablecmds.c:16845 +#: commands/tablecmds.c:16853 #, c-format msgid "table \"%s\" contains column \"%s\" not found in parent \"%s\"" msgstr "テーブル\"%1$s\"は親テーブル\"%3$s\"にない列\"%2$s\"を含んでいます" -#: commands/tablecmds.c:16848 +#: commands/tablecmds.c:16856 #, c-format msgid "The new partition may contain only the columns present in parent." msgstr "新しいパーティションは親に存在する列のみを含むことができます。" -#: commands/tablecmds.c:16860 +#: commands/tablecmds.c:16868 #, c-format msgid "trigger \"%s\" prevents table \"%s\" from becoming a partition" msgstr "トリガ\"%s\"のため、テーブル\"%s\"はパーティション子テーブルにはなれません" -#: commands/tablecmds.c:16862 commands/trigger.c:455 +#: commands/tablecmds.c:16870 commands/trigger.c:455 #, c-format msgid "ROW triggers with transition tables are not supported on partitions" msgstr "遷移テーブルを使用するROWトリガはパーティションではサポートされません" -#: commands/tablecmds.c:17041 +#: commands/tablecmds.c:17049 #, c-format msgid "cannot attach foreign table \"%s\" as partition of partitioned table \"%s\"" msgstr "外部テーブル\"%s\"はパーティションテーブル\"%s\"の子テーブルとしてアタッチすることはできません" -#: commands/tablecmds.c:17044 +#: commands/tablecmds.c:17052 #, c-format msgid "Table \"%s\" contains unique indexes." msgstr "テーブル\"%s\"はユニークインデックスを持っています。" -#: commands/tablecmds.c:17723 commands/tablecmds.c:17743 commands/tablecmds.c:17763 commands/tablecmds.c:17782 commands/tablecmds.c:17824 +#: commands/tablecmds.c:17731 commands/tablecmds.c:17751 commands/tablecmds.c:17771 commands/tablecmds.c:17790 commands/tablecmds.c:17832 #, c-format msgid "cannot attach index \"%s\" as a partition of index \"%s\"" msgstr "インデックス\"%s\"をインデックス\"%s\"の子インデックスとしてアタッチすることはできません" -#: commands/tablecmds.c:17726 +#: commands/tablecmds.c:17734 #, c-format msgid "Index \"%s\" is already attached to another index." msgstr "インデックス\"%s\"はすでに別のインデックスにアタッチされています。" -#: commands/tablecmds.c:17746 +#: commands/tablecmds.c:17754 #, c-format msgid "Index \"%s\" is not an index on any partition of table \"%s\"." msgstr "インデックス\"%s\"はテーブル\"%s\"のどの子テーブルのインデックスでもありません。" -#: commands/tablecmds.c:17766 +#: commands/tablecmds.c:17774 #, c-format msgid "The index definitions do not match." msgstr "インデックス定義が合致しません。" -#: commands/tablecmds.c:17785 +#: commands/tablecmds.c:17793 #, 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:17827 +#: commands/tablecmds.c:17835 #, c-format msgid "Another index is already attached for partition \"%s\"." msgstr "子テーブル\"%s\"にはすでに他のインデックスがアタッチされています。" @@ -10989,7 +10989,7 @@ msgid "skipping \"%s\" --- cannot vacuum non-tables or special system tables" msgstr "\"%s\"をスキップしています --- テーブルではないものや、特別なシステムテーブルに対してはVACUUMを実行できません" -#: commands/variable.c:165 utils/misc/guc.c:11229 utils/misc/guc.c:11291 +#: commands/variable.c:165 utils/misc/guc.c:11237 utils/misc/guc.c:11299 #, c-format msgid "Unrecognized key word: \"%s\"." msgstr "不明なキーワードです: \"%s\"" @@ -11184,7 +11184,7 @@ msgid "no value found for parameter %d" msgstr "パラメータ%dの値がありません" -#: executor/execExpr.c:893 parser/parse_agg.c:808 +#: executor/execExpr.c:893 parser/parse_agg.c:819 #, c-format msgid "window function calls cannot be nested" msgstr "ウィンドウ関数の呼び出しを入れ子にすることはできません" @@ -11206,7 +11206,7 @@ msgstr[0] "関数に%dを超える引数を渡せません" msgstr[1] "関数に%dを超える引数を渡せません" -#: 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 +#: executor/execExpr.c:2690 executor/execExpr.c:2696 executor/execExprInterp.c:2760 utils/adt/arrayfuncs.c:263 utils/adt/arrayfuncs.c:563 utils/adt/arrayfuncs.c:1305 utils/adt/arrayfuncs.c:3395 utils/adt/arrayfuncs.c:5357 utils/adt/arrayfuncs.c:5874 #, c-format msgid "number of array dimensions (%d) exceeds the maximum allowed (%d)" msgstr "配列の次数(%d)が上限(%d)を超えています" @@ -11251,7 +11251,8 @@ msgid "multidimensional arrays must have array expressions with matching dimensions" msgstr "多次元配列の配列式の次数があっていなければなりません" -#: 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 +#: executor/execExprInterp.c:2792 utils/adt/array_expanded.c:274 utils/adt/arrayfuncs.c:936 utils/adt/arrayfuncs.c:1523 utils/adt/arrayfuncs.c:2330 utils/adt/arrayfuncs.c:2345 utils/adt/arrayfuncs.c:2604 utils/adt/arrayfuncs.c:2620 utils/adt/arrayfuncs.c:2927 utils/adt/arrayfuncs.c:2942 utils/adt/arrayfuncs.c:3283 utils/adt/arrayfuncs.c:3425 utils/adt/arrayfuncs.c:5966 utils/adt/arrayfuncs.c:6307 utils/adt/arrayutils.c:88 utils/adt/arrayutils.c:97 +#: utils/adt/arrayutils.c:104 #, c-format msgid "array size exceeds the maximum allowed (%d)" msgstr "配列の次数が上限(%d)を超えています" @@ -11513,7 +11514,7 @@ msgid "concurrent delete, retrying" msgstr "並行する削除がありました、リトライします" -#: 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 +#: 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:3675 utils/adt/arrayfuncs.c:4195 utils/adt/arrayfuncs.c:6187 utils/adt/rowtypes.c:1182 #, c-format msgid "could not identify an equality operator for type %s" msgstr "型%sの等価性演算子を識別できませんでした" @@ -11687,7 +11688,7 @@ msgid "unexpected EOF for tape %d: requested %zu bytes, read %zu bytes" msgstr "テープ%dに対する予期しないEOF: %zuバイト要求しましたが、%zuバイト読み込みました" -#: executor/nodeAgg.c:4048 parser/parse_agg.c:650 parser/parse_agg.c:678 +#: executor/nodeAgg.c:4048 parser/parse_agg.c:661 parser/parse_agg.c:689 #, c-format msgid "aggregate function calls cannot be nested" msgstr "集約関数の呼び出しを入れ子にすることはできません" @@ -12364,7 +12365,7 @@ msgid "could not open configuration directory \"%s\": %m" msgstr "設定ディレクトリ\"%s\"をオープンできませんでした: %m" -#: jit/llvm/llvmjit.c:732 +#: jit/llvm/llvmjit.c:804 #, c-format msgid "time to inline: %.3fs, opt: %.3fs, emit: %.3fs" msgstr "所要時間: インライン化: %.3fs、最適化: %.3fs、出力: %.3fs" @@ -13954,7 +13955,7 @@ msgid "no data left in message" msgstr "メッセージ内にデータが残っていません" -#: libpq/pqformat.c:517 libpq/pqformat.c:535 libpq/pqformat.c:556 utils/adt/arrayfuncs.c:1460 utils/adt/rowtypes.c:567 +#: libpq/pqformat.c:517 libpq/pqformat.c:535 libpq/pqformat.c:556 utils/adt/arrayfuncs.c:1461 utils/adt/rowtypes.c:567 #, c-format msgid "insufficient data left in message" msgstr "メッセージ内に残るデータが不十分です" @@ -14600,306 +14601,306 @@ msgid "relation \"%s\" in %s clause not found in FROM clause" msgstr "%2$s句のリレーション\"%1$s\"はFROM句にありません" -#: parser/parse_agg.c:220 parser/parse_oper.c:222 +#: parser/parse_agg.c:208 parser/parse_oper.c:222 #, c-format msgid "could not identify an ordering operator for type %s" msgstr "型%sの順序演算子を識別できませんでした" -#: parser/parse_agg.c:222 +#: parser/parse_agg.c:210 #, c-format msgid "Aggregates with DISTINCT must be able to sort their inputs." msgstr "DISTINCT 付きの集約関数は、入力がソート可能である必要があります。" -#: parser/parse_agg.c:257 +#: parser/parse_agg.c:268 #, c-format msgid "GROUPING must have fewer than 32 arguments" msgstr "GROUPINGの引数は32より少くなければなりません" -#: parser/parse_agg.c:360 +#: parser/parse_agg.c:371 msgid "aggregate functions are not allowed in JOIN conditions" msgstr "JOIN条件で集約関数を使用できません" -#: parser/parse_agg.c:362 +#: parser/parse_agg.c:373 msgid "grouping operations are not allowed in JOIN conditions" msgstr "グルーピング演算はJOIN条件の中では使用できません" -#: parser/parse_agg.c:374 +#: parser/parse_agg.c:385 msgid "aggregate functions are not allowed in FROM clause of their own query level" msgstr "集約関数は自身の問い合わせレベルのFROM句の中では使用できません" -#: parser/parse_agg.c:376 +#: parser/parse_agg.c:387 msgid "grouping operations are not allowed in FROM clause of their own query level" msgstr "グルーピング演算は自身のクエリレベルのFROM句の中では使用できません" -#: parser/parse_agg.c:381 +#: parser/parse_agg.c:392 msgid "aggregate functions are not allowed in functions in FROM" msgstr "集約関数はFROM句内の関数では使用できません" -#: parser/parse_agg.c:383 +#: parser/parse_agg.c:394 msgid "grouping operations are not allowed in functions in FROM" msgstr "グルーピング演算はFROM句内の関数では使用できません" -#: parser/parse_agg.c:391 +#: parser/parse_agg.c:402 msgid "aggregate functions are not allowed in policy expressions" msgstr "集約関数はポリシ式では使用できません" -#: parser/parse_agg.c:393 +#: parser/parse_agg.c:404 msgid "grouping operations are not allowed in policy expressions" msgstr "グルーピング演算はポリシ式では使用できません" -#: parser/parse_agg.c:410 +#: parser/parse_agg.c:421 msgid "aggregate functions are not allowed in window RANGE" msgstr "集約関数はウィンドウRANGEの中では集約関数を使用できません" -#: parser/parse_agg.c:412 +#: parser/parse_agg.c:423 msgid "grouping operations are not allowed in window RANGE" msgstr "ウィンドウ定義のRANGE句の中ではグルーピング演算は使用できません" -#: parser/parse_agg.c:417 +#: parser/parse_agg.c:428 msgid "aggregate functions are not allowed in window ROWS" msgstr "ウィンドウ定義のROWS句では集約関数は使用できません" -#: parser/parse_agg.c:419 +#: parser/parse_agg.c:430 msgid "grouping operations are not allowed in window ROWS" msgstr "ウィンドウ定義のROWS句ではグルーピング演算は使用できません" -#: parser/parse_agg.c:424 +#: parser/parse_agg.c:435 msgid "aggregate functions are not allowed in window GROUPS" msgstr "ウィンドウ定義のGROUPS句では集約関数は使用できません" -#: parser/parse_agg.c:426 +#: parser/parse_agg.c:437 msgid "grouping operations are not allowed in window GROUPS" msgstr "ウィンドウ定義のGROUPS句ではグルーピング演算は使用できません" -#: parser/parse_agg.c:460 +#: parser/parse_agg.c:471 msgid "aggregate functions are not allowed in check constraints" msgstr "検査制約では集約関数を使用できません" -#: parser/parse_agg.c:462 +#: parser/parse_agg.c:473 msgid "grouping operations are not allowed in check constraints" msgstr "検査制約ではグルーピング演算を使用できません" -#: parser/parse_agg.c:469 +#: parser/parse_agg.c:480 msgid "aggregate functions are not allowed in DEFAULT expressions" msgstr "DEFAULT式では集約関数を使用できません" -#: parser/parse_agg.c:471 +#: parser/parse_agg.c:482 msgid "grouping operations are not allowed in DEFAULT expressions" msgstr "DEFAULT式ではグルーピング演算を使用できません" -#: parser/parse_agg.c:476 +#: parser/parse_agg.c:487 msgid "aggregate functions are not allowed in index expressions" msgstr "インデックス式では集約関数を使用できません" -#: parser/parse_agg.c:478 +#: parser/parse_agg.c:489 msgid "grouping operations are not allowed in index expressions" msgstr "インデックス式ではグルーピング演算を使用できません" -#: parser/parse_agg.c:483 +#: parser/parse_agg.c:494 msgid "aggregate functions are not allowed in index predicates" msgstr "インデックス述語では集約関数を使用できません" -#: parser/parse_agg.c:485 +#: parser/parse_agg.c:496 msgid "grouping operations are not allowed in index predicates" msgstr "インデックス述語ではグルーピング演算を使用できません" -#: parser/parse_agg.c:490 +#: parser/parse_agg.c:501 msgid "aggregate functions are not allowed in transform expressions" msgstr "変換式では集約関数を使用できません" -#: parser/parse_agg.c:492 +#: parser/parse_agg.c:503 msgid "grouping operations are not allowed in transform expressions" msgstr "変換式ではグルーピング演算を使用できません" -#: parser/parse_agg.c:497 +#: parser/parse_agg.c:508 msgid "aggregate functions are not allowed in EXECUTE parameters" msgstr "EXECUTEのパラメータでは集約関数を使用できません" -#: parser/parse_agg.c:499 +#: parser/parse_agg.c:510 msgid "grouping operations are not allowed in EXECUTE parameters" msgstr "EXECUTEのパラメータではグルーピング演算を使用できません" -#: parser/parse_agg.c:504 +#: parser/parse_agg.c:515 msgid "aggregate functions are not allowed in trigger WHEN conditions" msgstr "トリガのWHEN条件では集約関数を使用できません" -#: parser/parse_agg.c:506 +#: parser/parse_agg.c:517 msgid "grouping operations are not allowed in trigger WHEN conditions" msgstr "トリガのWHEN条件ではグルーピング演算を使用できません" -#: parser/parse_agg.c:511 +#: parser/parse_agg.c:522 msgid "aggregate functions are not allowed in partition bound" msgstr "集約関数はパーティション境界では使用できません" -#: parser/parse_agg.c:513 +#: parser/parse_agg.c:524 msgid "grouping operations are not allowed in partition bound" msgstr "グルーピング演算はパーティション境界では使用できません" -#: parser/parse_agg.c:518 +#: parser/parse_agg.c:529 msgid "aggregate functions are not allowed in partition key expressions" msgstr "パーティションキー式では集約関数は使用できません" -#: parser/parse_agg.c:520 +#: parser/parse_agg.c:531 msgid "grouping operations are not allowed in partition key expressions" msgstr "パーティションキー式ではグルーピング演算は使用できません" -#: parser/parse_agg.c:526 +#: parser/parse_agg.c:537 msgid "aggregate functions are not allowed in column generation expressions" msgstr "集約関数はカラム生成式では使用できません" -#: parser/parse_agg.c:528 +#: parser/parse_agg.c:539 msgid "grouping operations are not allowed in column generation expressions" msgstr "グルーピング演算はカラム生成式では使用できません" -#: parser/parse_agg.c:534 +#: parser/parse_agg.c:545 msgid "aggregate functions are not allowed in CALL arguments" msgstr "CALLの引数では集約関数を使用できません" -#: parser/parse_agg.c:536 +#: parser/parse_agg.c:547 msgid "grouping operations are not allowed in CALL arguments" msgstr "CALLの引数ではグルーピング演算を使用できません" -#: parser/parse_agg.c:542 +#: parser/parse_agg.c:553 msgid "aggregate functions are not allowed in COPY FROM WHERE conditions" msgstr "集約関数は COPY FROM の WHERE 条件では使用できません" -#: parser/parse_agg.c:544 +#: parser/parse_agg.c:555 msgid "grouping operations are not allowed in COPY FROM WHERE conditions" msgstr "グルーピング演算は COPY FROM の WHERE 条件の中では使用できません" #. translator: %s is name of a SQL construct, eg GROUP BY -#: parser/parse_agg.c:567 parser/parse_clause.c:1816 +#: parser/parse_agg.c:578 parser/parse_clause.c:1816 #, c-format msgid "aggregate functions are not allowed in %s" msgstr "%sでは集約関数を使用できません" #. translator: %s is name of a SQL construct, eg GROUP BY -#: parser/parse_agg.c:570 +#: parser/parse_agg.c:581 #, c-format msgid "grouping operations are not allowed in %s" msgstr "%sではグルーピング演算を使用できません" -#: parser/parse_agg.c:671 +#: parser/parse_agg.c:682 #, c-format msgid "outer-level aggregate cannot contain a lower-level variable in its direct arguments" msgstr "アウタレベルの集約は直接引数に低位の変数を含むことができません" -#: parser/parse_agg.c:749 +#: parser/parse_agg.c:760 #, c-format msgid "aggregate function calls cannot contain set-returning function calls" msgstr "集合返却関数の呼び出しに集約関数の呼び出しを含むことはできません" -#: parser/parse_agg.c:750 parser/parse_expr.c:1850 parser/parse_expr.c:2345 parser/parse_func.c:872 +#: parser/parse_agg.c:761 parser/parse_expr.c:1850 parser/parse_expr.c:2345 parser/parse_func.c:872 #, c-format msgid "You might be able to move the set-returning function into a LATERAL FROM item." msgstr "この集合返却関数をLATERAL FROM項目に移動できるかもしれません。" -#: parser/parse_agg.c:755 +#: parser/parse_agg.c:766 #, c-format msgid "aggregate function calls cannot contain window function calls" msgstr "集約関数の呼び出しにウィンドウ関数の呼び出しを含むことはできません" -#: parser/parse_agg.c:834 +#: parser/parse_agg.c:845 msgid "window functions are not allowed in JOIN conditions" msgstr "JOIN条件ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:841 +#: parser/parse_agg.c:852 msgid "window functions are not allowed in functions in FROM" msgstr "FROM句内の関数ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:847 +#: parser/parse_agg.c:858 msgid "window functions are not allowed in policy expressions" msgstr "ポリシ式ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:860 +#: parser/parse_agg.c:871 msgid "window functions are not allowed in window definitions" msgstr "ウィンドウ定義ではウィンドウ関数は使用できません" -#: parser/parse_agg.c:892 +#: parser/parse_agg.c:903 msgid "window functions are not allowed in check constraints" msgstr "検査制約の中ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:896 +#: parser/parse_agg.c:907 msgid "window functions are not allowed in DEFAULT expressions" msgstr "DEFAULT式の中ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:899 +#: parser/parse_agg.c:910 msgid "window functions are not allowed in index expressions" msgstr "インデックス式ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:902 +#: parser/parse_agg.c:913 msgid "window functions are not allowed in index predicates" msgstr "インデックス述語ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:905 +#: parser/parse_agg.c:916 msgid "window functions are not allowed in transform expressions" msgstr "変換式ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:908 +#: parser/parse_agg.c:919 msgid "window functions are not allowed in EXECUTE parameters" msgstr "EXECUTEパラメータではウィンドウ関数を使用できません" -#: parser/parse_agg.c:911 +#: parser/parse_agg.c:922 msgid "window functions are not allowed in trigger WHEN conditions" msgstr "トリガのWHEN条件ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:914 +#: parser/parse_agg.c:925 msgid "window functions are not allowed in partition bound" msgstr "ウィンドウ関数はパーティション境界では使用できません" -#: parser/parse_agg.c:917 +#: parser/parse_agg.c:928 msgid "window functions are not allowed in partition key expressions" msgstr "パーティションキー式ではウィンドウ関数は使用できません" -#: parser/parse_agg.c:920 +#: parser/parse_agg.c:931 msgid "window functions are not allowed in CALL arguments" msgstr "CALLの引数ではウィンドウ関数は使用できません" -#: parser/parse_agg.c:923 +#: parser/parse_agg.c:934 msgid "window functions are not allowed in COPY FROM WHERE conditions" msgstr "ウィンドウ関数は COPY FROM の WHERE 条件では使用できません" -#: parser/parse_agg.c:926 +#: parser/parse_agg.c:937 msgid "window functions are not allowed in column generation expressions" msgstr "ウィンドウ関数はカラム生成式では使用できません" #. translator: %s is name of a SQL construct, eg GROUP BY -#: parser/parse_agg.c:946 parser/parse_clause.c:1825 +#: parser/parse_agg.c:957 parser/parse_clause.c:1825 #, c-format msgid "window functions are not allowed in %s" msgstr "%sの中ではウィンドウ関数を使用できません" -#: parser/parse_agg.c:980 parser/parse_clause.c:2659 +#: parser/parse_agg.c:991 parser/parse_clause.c:2659 #, c-format msgid "window \"%s\" does not exist" msgstr "ウィンドウ\"%s\"は存在しません" -#: parser/parse_agg.c:1064 +#: parser/parse_agg.c:1075 #, c-format msgid "too many grouping sets present (maximum 4096)" msgstr "グルーピングセットの数が多すぎます (最大4096)" -#: parser/parse_agg.c:1204 +#: parser/parse_agg.c:1215 #, c-format msgid "aggregate functions are not allowed in a recursive query's recursive term" msgstr "再帰問い合わせの再帰項では集約関数を使用できません" -#: parser/parse_agg.c:1397 +#: parser/parse_agg.c:1408 #, c-format msgid "column \"%s.%s\" must appear in the GROUP BY clause or be used in an aggregate function" msgstr "列\"%s.%s\"はGROUP BY句で指定するか、集約関数内で使用しなければなりません" -#: parser/parse_agg.c:1400 +#: parser/parse_agg.c:1411 #, c-format msgid "Direct arguments of an ordered-set aggregate must use only grouped columns." msgstr "順序集合集約の直接引数はグルーピングされた列のみを使用しなければなりません。" -#: parser/parse_agg.c:1405 +#: parser/parse_agg.c:1416 #, c-format msgid "subquery uses ungrouped column \"%s.%s\" from outer query" msgstr "外部問い合わせから副問い合わせがグループ化されていない列\"%s.%s\"を使用しています" -#: parser/parse_agg.c:1569 +#: parser/parse_agg.c:1580 #, c-format msgid "arguments to GROUPING must be grouping expressions of the associated query level" msgstr "GROUPINGの引数は関連するクエリレベルのグルーピング式でなければなりません" @@ -16390,11 +16391,6 @@ msgid "index \"%s\" is already associated with a constraint" msgstr "インデックス\"%s\"はすでに1つの制約に割り当てられています" -#: parser/parse_utilcmd.c:2243 -#, c-format -msgid "index \"%s\" is not valid" -msgstr "インデックス\"%s\"は有効ではありません" - #: parser/parse_utilcmd.c:2249 #, c-format msgid "\"%s\" is not a unique index" @@ -16760,12 +16756,12 @@ msgid "huge pages not supported with the current shared_memory_type setting" msgstr "ヒュージページは現在のshared_memory_typeの設定ではサポートされません" -#: port/pg_shmem.c:725 port/sysv_shmem.c:725 utils/init/miscinit.c:1142 +#: port/pg_shmem.c:725 port/sysv_shmem.c:725 utils/init/miscinit.c:1150 #, c-format msgid "pre-existing shared memory block (key %lu, ID %lu) is still in use" msgstr "既存の共有メモリブロック(キー%lu、ID %lu)がまだ使用中です" -#: port/pg_shmem.c:728 port/sysv_shmem.c:728 utils/init/miscinit.c:1144 +#: port/pg_shmem.c:728 port/sysv_shmem.c:728 utils/init/miscinit.c:1152 #, c-format msgid "Terminate any old server processes associated with data directory \"%s\"." msgstr "データディレクトリ \"%s\". に対応する古いサーバプロセスをすべて終了させてください。" @@ -17190,48 +17186,48 @@ msgid "Target must be \"archiver\" or \"bgwriter\"." msgstr "対象は\"archiver\"または\"bgwriter\"でなければなりません" -#: postmaster/pgstat.c:4570 +#: postmaster/pgstat.c:4571 #, c-format msgid "could not read statistics message: %m" msgstr "統計情報メッセージを読み取れませんでした: %m" -#: postmaster/pgstat.c:4892 postmaster/pgstat.c:5055 +#: postmaster/pgstat.c:4893 postmaster/pgstat.c:5056 #, c-format msgid "could not open temporary statistics file \"%s\": %m" msgstr "一時統計情報ファイル\"%s\"をオープンできませんでした: %m" -#: postmaster/pgstat.c:4965 postmaster/pgstat.c:5100 +#: postmaster/pgstat.c:4966 postmaster/pgstat.c:5101 #, c-format msgid "could not write temporary statistics file \"%s\": %m" msgstr "一時統計情報ファイル\"%s\"に書き込みできませんでした: %m" -#: postmaster/pgstat.c:4974 postmaster/pgstat.c:5109 +#: postmaster/pgstat.c:4975 postmaster/pgstat.c:5110 #, c-format msgid "could not close temporary statistics file \"%s\": %m" msgstr "一時統計情報ファイル\"%s\"をクローズできませんでした: %m" -#: postmaster/pgstat.c:4982 postmaster/pgstat.c:5117 +#: postmaster/pgstat.c:4983 postmaster/pgstat.c:5118 #, c-format msgid "could not rename temporary statistics file \"%s\" to \"%s\": %m" msgstr "一時統計情報ファイル\"%s\"の名前を\"%s\"に変更できませんでした: %m" -#: postmaster/pgstat.c:5214 postmaster/pgstat.c:5431 postmaster/pgstat.c:5585 +#: postmaster/pgstat.c:5215 postmaster/pgstat.c:5432 postmaster/pgstat.c:5586 #, c-format msgid "could not open statistics file \"%s\": %m" msgstr "統計情報ファイル\"%s\"をオープンできませんでした: %m" -#: postmaster/pgstat.c:5226 postmaster/pgstat.c:5236 postmaster/pgstat.c:5257 postmaster/pgstat.c:5268 postmaster/pgstat.c:5290 postmaster/pgstat.c:5305 postmaster/pgstat.c:5368 postmaster/pgstat.c:5443 postmaster/pgstat.c:5463 postmaster/pgstat.c:5481 postmaster/pgstat.c:5497 postmaster/pgstat.c:5515 postmaster/pgstat.c:5531 postmaster/pgstat.c:5597 postmaster/pgstat.c:5609 postmaster/pgstat.c:5621 postmaster/pgstat.c:5632 postmaster/pgstat.c:5657 -#: postmaster/pgstat.c:5679 +#: postmaster/pgstat.c:5227 postmaster/pgstat.c:5237 postmaster/pgstat.c:5258 postmaster/pgstat.c:5269 postmaster/pgstat.c:5291 postmaster/pgstat.c:5306 postmaster/pgstat.c:5369 postmaster/pgstat.c:5444 postmaster/pgstat.c:5464 postmaster/pgstat.c:5482 postmaster/pgstat.c:5498 postmaster/pgstat.c:5516 postmaster/pgstat.c:5532 postmaster/pgstat.c:5598 postmaster/pgstat.c:5610 postmaster/pgstat.c:5622 postmaster/pgstat.c:5633 postmaster/pgstat.c:5658 +#: postmaster/pgstat.c:5680 #, c-format msgid "corrupted statistics file \"%s\"" msgstr "統計情報ファイル\"%s\"が破損しています" -#: postmaster/pgstat.c:5808 +#: postmaster/pgstat.c:5809 #, c-format msgid "using stale statistics instead of current ones because stats collector is not responding" msgstr "統計情報コレクタが応答しないため、最新の統計値の替わりに古い値を使用します" -#: postmaster/pgstat.c:6138 +#: postmaster/pgstat.c:6139 #, c-format msgid "database hash table corrupted during cleanup --- abort" msgstr "整理処理においてデータベースハッシュテーブルが破損しました --- 中断します" @@ -17291,7 +17287,7 @@ msgid "starting %s" msgstr "%s を起動しています" -#: postmaster/postmaster.c:1157 postmaster/postmaster.c:1255 utils/init/miscinit.c:1602 +#: postmaster/postmaster.c:1157 postmaster/postmaster.c:1255 utils/init/miscinit.c:1610 #, c-format msgid "invalid list syntax in parameter \"%s\"" msgstr "パラメータ\"%s\"のリスト構文が不正です" @@ -17417,7 +17413,7 @@ msgid "unsupported frontend protocol %u.%u: server supports %u.0 to %u.%u" msgstr "フロントエンドプロトコル%u.%uをサポートしていません: サーバは%u.0から %u.%uまでをサポートします" -#: postmaster/postmaster.c:2203 utils/misc/guc.c:6781 utils/misc/guc.c:6817 utils/misc/guc.c:6887 utils/misc/guc.c:8238 utils/misc/guc.c:11110 utils/misc/guc.c:11151 +#: postmaster/postmaster.c:2203 utils/misc/guc.c:6781 utils/misc/guc.c:6817 utils/misc/guc.c:6887 utils/misc/guc.c:8238 utils/misc/guc.c:11118 utils/misc/guc.c:11159 #, c-format msgid "invalid value for parameter \"%s\": \"%s\"" msgstr "パラメータ\"%s\"の値が不正です: \"%s\"" @@ -19788,12 +19784,12 @@ msgid "database \"%s\" is being used by prepared transactions" msgstr "データベース\"%s\"は準備済みトランザクションで使用中です" -#: storage/ipc/procarray.c:3159 storage/ipc/signalfuncs.c:142 +#: storage/ipc/procarray.c:3159 storage/ipc/signalfuncs.c:147 #, c-format msgid "must be a superuser to terminate superuser process" msgstr "スーパユーザのプロセスを終了させるにはスーパユーザである必要があります" -#: storage/ipc/procarray.c:3166 storage/ipc/signalfuncs.c:147 +#: storage/ipc/procarray.c:3166 storage/ipc/signalfuncs.c:152 #, 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のメンバである必要があります。" @@ -19843,33 +19839,33 @@ msgid "PID %d is not a PostgreSQL server process" msgstr "PID %dはPostgreSQLサーバプロセスではありません" -#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1372 +#: storage/ipc/signalfuncs.c:103 storage/lmgr/proc.c:1380 #, c-format msgid "could not send signal to process %d: %m" msgstr "プロセス%dにシグナルを送信できませんでした: %m" -#: storage/ipc/signalfuncs.c:118 +#: storage/ipc/signalfuncs.c:123 #, c-format msgid "must be a superuser to cancel superuser query" msgstr "スーパユーザの問い合わせをキャンセルするにはスーパユーザである必要があります" -#: storage/ipc/signalfuncs.c:123 +#: storage/ipc/signalfuncs.c:128 #, c-format msgid "must be a member of the role whose query is being canceled or member of pg_signal_backend" msgstr "キャンセルしようとしている問い合わせのロールまたはpg_signal_backendのメンバである必要があります" -#: storage/ipc/signalfuncs.c:183 +#: storage/ipc/signalfuncs.c:188 #, c-format msgid "must be superuser to rotate log files with adminpack 1.0" msgstr "adminpack 1.0 でログファイルをローテートするにはスーパユーザである必要があります" #. translator: %s is a SQL function name -#: storage/ipc/signalfuncs.c:185 utils/adt/genfile.c:253 +#: storage/ipc/signalfuncs.c:190 utils/adt/genfile.c:253 #, c-format msgid "Consider using %s, which is part of core, instead." msgstr "代わりにコアの一部である %s の使用を検討してください。" -#: storage/ipc/signalfuncs.c:191 storage/ipc/signalfuncs.c:211 +#: storage/ipc/signalfuncs.c:196 storage/ipc/signalfuncs.c:216 #, c-format msgid "rotation not possible because log collection not active" msgstr "ログ収集が活動していませんのでローテーションを行うことができません" @@ -20109,37 +20105,37 @@ msgid "number of requested standby connections exceeds max_wal_senders (currently %d)" msgstr "要求されたスタンバイ接続が max_wal_senders を超えています（現在は %d）" -#: storage/lmgr/proc.c:1343 +#: storage/lmgr/proc.c:1351 #, c-format msgid "Process %d waits for %s on %s." msgstr "プロセス%dは%sを%sで待機しています。" -#: storage/lmgr/proc.c:1354 +#: storage/lmgr/proc.c:1362 #, c-format msgid "sending cancel to blocking autovacuum PID %d" msgstr "ブロックしている自動VACUUMプロセスのPID %dへキャンセルを送付しています" -#: storage/lmgr/proc.c:1474 +#: storage/lmgr/proc.c:1482 #, 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:1489 +#: storage/lmgr/proc.c:1497 #, 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:1498 +#: storage/lmgr/proc.c:1506 #, 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:1505 +#: storage/lmgr/proc.c:1513 #, 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:1521 +#: storage/lmgr/proc.c:1529 #, 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を獲得することに失敗しました" @@ -21026,238 +21022,238 @@ msgid "initial position must not be null" msgstr "初期位置nullであってはなりません" -#: utils/adt/arrayfuncs.c:270 utils/adt/arrayfuncs.c:284 utils/adt/arrayfuncs.c:295 utils/adt/arrayfuncs.c:317 utils/adt/arrayfuncs.c:332 utils/adt/arrayfuncs.c:346 utils/adt/arrayfuncs.c:352 utils/adt/arrayfuncs.c:359 utils/adt/arrayfuncs.c:492 utils/adt/arrayfuncs.c:508 utils/adt/arrayfuncs.c:519 utils/adt/arrayfuncs.c:534 utils/adt/arrayfuncs.c:555 utils/adt/arrayfuncs.c:585 utils/adt/arrayfuncs.c:592 utils/adt/arrayfuncs.c:600 utils/adt/arrayfuncs.c:634 -#: utils/adt/arrayfuncs.c:657 utils/adt/arrayfuncs.c:677 utils/adt/arrayfuncs.c:789 utils/adt/arrayfuncs.c:798 utils/adt/arrayfuncs.c:828 utils/adt/arrayfuncs.c:843 utils/adt/arrayfuncs.c:896 +#: utils/adt/arrayfuncs.c:271 utils/adt/arrayfuncs.c:285 utils/adt/arrayfuncs.c:296 utils/adt/arrayfuncs.c:318 utils/adt/arrayfuncs.c:333 utils/adt/arrayfuncs.c:347 utils/adt/arrayfuncs.c:353 utils/adt/arrayfuncs.c:360 utils/adt/arrayfuncs.c:493 utils/adt/arrayfuncs.c:509 utils/adt/arrayfuncs.c:520 utils/adt/arrayfuncs.c:535 utils/adt/arrayfuncs.c:556 utils/adt/arrayfuncs.c:586 utils/adt/arrayfuncs.c:593 utils/adt/arrayfuncs.c:601 utils/adt/arrayfuncs.c:635 +#: utils/adt/arrayfuncs.c:658 utils/adt/arrayfuncs.c:678 utils/adt/arrayfuncs.c:790 utils/adt/arrayfuncs.c:799 utils/adt/arrayfuncs.c:829 utils/adt/arrayfuncs.c:844 utils/adt/arrayfuncs.c:897 #, c-format msgid "malformed array literal: \"%s\"" msgstr "配列リテラルの書式が誤っています: \"%s\"" -#: utils/adt/arrayfuncs.c:271 +#: utils/adt/arrayfuncs.c:272 #, c-format msgid "\"[\" must introduce explicitly-specified array dimensions." msgstr "\"[\"は配列次元の明示的な指定の先頭である必要があります。" -#: utils/adt/arrayfuncs.c:285 +#: utils/adt/arrayfuncs.c:286 #, c-format msgid "Missing array dimension value." msgstr "配列の次元数の値がありません。" -#: utils/adt/arrayfuncs.c:296 utils/adt/arrayfuncs.c:333 +#: utils/adt/arrayfuncs.c:297 utils/adt/arrayfuncs.c:334 #, c-format msgid "Missing \"%s\" after array dimensions." msgstr "配列の次元の後に\"%s\"がありません。" -#: utils/adt/arrayfuncs.c:305 utils/adt/arrayfuncs.c:2882 utils/adt/arrayfuncs.c:2914 utils/adt/arrayfuncs.c:2929 +#: utils/adt/arrayfuncs.c:306 utils/adt/arrayfuncs.c:2918 utils/adt/arrayfuncs.c:2963 utils/adt/arrayfuncs.c:2978 #, c-format msgid "upper bound cannot be less than lower bound" msgstr "上限を下限より小さくすることはできません" -#: utils/adt/arrayfuncs.c:318 +#: utils/adt/arrayfuncs.c:319 #, c-format msgid "Array value must start with \"{\" or dimension information." msgstr "配列値は\"{\"または次元情報から始まる必要があります。" -#: utils/adt/arrayfuncs.c:347 +#: utils/adt/arrayfuncs.c:348 #, c-format msgid "Array contents must start with \"{\"." msgstr "配列の内容は\"{\"で始まる必要があります。" -#: utils/adt/arrayfuncs.c:353 utils/adt/arrayfuncs.c:360 +#: utils/adt/arrayfuncs.c:354 utils/adt/arrayfuncs.c:361 #, c-format msgid "Specified array dimensions do not match array contents." msgstr "指定された配列の次元数が配列の内容と合致していません。" -#: utils/adt/arrayfuncs.c:493 utils/adt/arrayfuncs.c:520 utils/adt/rangetypes.c:2181 utils/adt/rangetypes.c:2189 utils/adt/rowtypes.c:210 utils/adt/rowtypes.c:218 +#: utils/adt/arrayfuncs.c:494 utils/adt/arrayfuncs.c:521 utils/adt/rangetypes.c:2181 utils/adt/rangetypes.c:2189 utils/adt/rowtypes.c:210 utils/adt/rowtypes.c:218 #, c-format msgid "Unexpected end of input." msgstr "想定外の入力の終端。" -#: utils/adt/arrayfuncs.c:509 utils/adt/arrayfuncs.c:556 utils/adt/arrayfuncs.c:586 utils/adt/arrayfuncs.c:635 +#: utils/adt/arrayfuncs.c:510 utils/adt/arrayfuncs.c:557 utils/adt/arrayfuncs.c:587 utils/adt/arrayfuncs.c:636 #, c-format msgid "Unexpected \"%c\" character." msgstr "想定外の文字\"%c\"。" -#: utils/adt/arrayfuncs.c:535 utils/adt/arrayfuncs.c:658 +#: utils/adt/arrayfuncs.c:536 utils/adt/arrayfuncs.c:659 #, c-format msgid "Unexpected array element." msgstr "想定外の配列要素。" -#: utils/adt/arrayfuncs.c:593 +#: utils/adt/arrayfuncs.c:594 #, c-format msgid "Unmatched \"%c\" character." msgstr "対応しない\"%c\"文字。" -#: utils/adt/arrayfuncs.c:601 utils/adt/jsonfuncs.c:2452 +#: utils/adt/arrayfuncs.c:602 utils/adt/jsonfuncs.c:2452 #, c-format msgid "Multidimensional arrays must have sub-arrays with matching dimensions." msgstr "多次元配列は合致する次元の副配列を持たなければなりません。" -#: utils/adt/arrayfuncs.c:678 +#: utils/adt/arrayfuncs.c:679 #, c-format msgid "Junk after closing right brace." msgstr "右括弧の後にごみがあります。" -#: utils/adt/arrayfuncs.c:1300 utils/adt/arrayfuncs.c:3342 utils/adt/arrayfuncs.c:5821 +#: utils/adt/arrayfuncs.c:1301 utils/adt/arrayfuncs.c:3391 utils/adt/arrayfuncs.c:5870 #, c-format msgid "invalid number of dimensions: %d" msgstr "不正な次元数: %d" -#: utils/adt/arrayfuncs.c:1311 +#: utils/adt/arrayfuncs.c:1312 #, c-format msgid "invalid array flags" msgstr "不正な配列フラグ" -#: utils/adt/arrayfuncs.c:1319 +#: utils/adt/arrayfuncs.c:1320 #, c-format msgid "wrong element type" msgstr "間違った要素型" -#: utils/adt/arrayfuncs.c:1356 utils/adt/rangetypes.c:335 utils/cache/lsyscache.c:2862 +#: utils/adt/arrayfuncs.c:1357 utils/adt/rangetypes.c:335 utils/cache/lsyscache.c:2862 #, c-format msgid "no binary input function available for type %s" msgstr "型%sにはバイナリ入力関数がありません" -#: utils/adt/arrayfuncs.c:1496 +#: utils/adt/arrayfuncs.c:1497 #, c-format msgid "improper binary format in array element %d" msgstr "配列要素%dのバイナリ書式が不適切です" -#: utils/adt/arrayfuncs.c:1577 utils/adt/rangetypes.c:340 utils/cache/lsyscache.c:2895 +#: utils/adt/arrayfuncs.c:1578 utils/adt/rangetypes.c:340 utils/cache/lsyscache.c:2895 #, c-format msgid "no binary output function available for type %s" msgstr "型%sにはバイナリ出力関数がありません" -#: utils/adt/arrayfuncs.c:2055 +#: utils/adt/arrayfuncs.c:2056 #, c-format msgid "slices of fixed-length arrays not implemented" msgstr "固定長配列の部分配列は実装されていません" -#: utils/adt/arrayfuncs.c:2233 utils/adt/arrayfuncs.c:2255 utils/adt/arrayfuncs.c:2304 utils/adt/arrayfuncs.c:2542 utils/adt/arrayfuncs.c:2860 utils/adt/arrayfuncs.c:5807 utils/adt/arrayfuncs.c:5833 utils/adt/arrayfuncs.c:5844 utils/adt/json.c:1141 utils/adt/json.c:1216 utils/adt/jsonb.c:1316 utils/adt/jsonb.c:1402 utils/adt/jsonfuncs.c:4340 utils/adt/jsonfuncs.c:4490 utils/adt/jsonfuncs.c:4602 utils/adt/jsonfuncs.c:4648 +#: utils/adt/arrayfuncs.c:2234 utils/adt/arrayfuncs.c:2256 utils/adt/arrayfuncs.c:2305 utils/adt/arrayfuncs.c:2559 utils/adt/arrayfuncs.c:2893 utils/adt/arrayfuncs.c:5856 utils/adt/arrayfuncs.c:5882 utils/adt/arrayfuncs.c:5893 utils/adt/json.c:1141 utils/adt/json.c:1216 utils/adt/jsonb.c:1316 utils/adt/jsonb.c:1402 utils/adt/jsonfuncs.c:4340 utils/adt/jsonfuncs.c:4490 utils/adt/jsonfuncs.c:4602 utils/adt/jsonfuncs.c:4648 #, c-format msgid "wrong number of array subscripts" msgstr "配列の添え字が不正な数値です" -#: utils/adt/arrayfuncs.c:2238 utils/adt/arrayfuncs.c:2346 utils/adt/arrayfuncs.c:2606 utils/adt/arrayfuncs.c:2919 +#: utils/adt/arrayfuncs.c:2239 utils/adt/arrayfuncs.c:2363 utils/adt/arrayfuncs.c:2639 utils/adt/arrayfuncs.c:2968 #, c-format msgid "array subscript out of range" msgstr "配列の添え字が範囲外です" -#: utils/adt/arrayfuncs.c:2243 +#: utils/adt/arrayfuncs.c:2244 #, c-format msgid "cannot assign null value to an element of a fixed-length array" msgstr "固定長配列の要素にNULL値を代入できません" -#: utils/adt/arrayfuncs.c:2807 +#: utils/adt/arrayfuncs.c:2840 #, c-format msgid "updates on slices of fixed-length arrays not implemented" msgstr "固定長配列の部分配列の更新は実装されていません" -#: utils/adt/arrayfuncs.c:2838 +#: utils/adt/arrayfuncs.c:2871 #, c-format msgid "array slice subscript must provide both boundaries" msgstr "配列のスライスの添え字は両方の境界を示す必要があります" -#: utils/adt/arrayfuncs.c:2839 +#: utils/adt/arrayfuncs.c:2872 #, c-format msgid "When assigning to a slice of an empty array value, slice boundaries must be fully specified." msgstr "空の配列値のスライスに代入するには、スライスの範囲は完全に指定する必要があります。" -#: utils/adt/arrayfuncs.c:2850 utils/adt/arrayfuncs.c:2946 +#: utils/adt/arrayfuncs.c:2883 utils/adt/arrayfuncs.c:2995 #, c-format msgid "source array too small" msgstr "元の配列が小さすぎます" -#: utils/adt/arrayfuncs.c:3500 +#: utils/adt/arrayfuncs.c:3549 #, c-format msgid "null array element not allowed in this context" msgstr "この文脈ではNULLの配列要素は許可されません" -#: utils/adt/arrayfuncs.c:3602 utils/adt/arrayfuncs.c:3773 utils/adt/arrayfuncs.c:4129 +#: utils/adt/arrayfuncs.c:3651 utils/adt/arrayfuncs.c:3822 utils/adt/arrayfuncs.c:4178 #, c-format msgid "cannot compare arrays of different element types" msgstr "要素型の異なる配列を比較できません" -#: utils/adt/arrayfuncs.c:3951 utils/adt/rangetypes.c:1254 utils/adt/rangetypes.c:1318 +#: utils/adt/arrayfuncs.c:4000 utils/adt/rangetypes.c:1254 utils/adt/rangetypes.c:1318 #, c-format msgid "could not identify a hash function for type %s" msgstr "型 %s のハッシュ関数を識別できません" -#: utils/adt/arrayfuncs.c:4044 +#: utils/adt/arrayfuncs.c:4093 #, c-format msgid "could not identify an extended hash function for type %s" msgstr "型 %s の拡張ハッシュ関数を特定できませんでした" -#: utils/adt/arrayfuncs.c:5221 +#: utils/adt/arrayfuncs.c:5270 #, c-format msgid "data type %s is not an array type" msgstr "データ型%sは配列型ではありません" -#: utils/adt/arrayfuncs.c:5276 +#: utils/adt/arrayfuncs.c:5325 #, c-format msgid "cannot accumulate null arrays" msgstr "null配列は連結できません" -#: utils/adt/arrayfuncs.c:5304 +#: utils/adt/arrayfuncs.c:5353 #, c-format msgid "cannot accumulate empty arrays" msgstr "空の配列は連結できません" -#: utils/adt/arrayfuncs.c:5331 utils/adt/arrayfuncs.c:5337 +#: utils/adt/arrayfuncs.c:5380 utils/adt/arrayfuncs.c:5386 #, c-format msgid "cannot accumulate arrays of different dimensionality" msgstr "次元の異なる配列は結合できません" -#: utils/adt/arrayfuncs.c:5705 utils/adt/arrayfuncs.c:5745 +#: utils/adt/arrayfuncs.c:5754 utils/adt/arrayfuncs.c:5794 #, c-format msgid "dimension array or low bound array cannot be null" msgstr "次元配列もしくは下限値配列が NULL であってはなりません" -#: utils/adt/arrayfuncs.c:5808 utils/adt/arrayfuncs.c:5834 +#: utils/adt/arrayfuncs.c:5857 utils/adt/arrayfuncs.c:5883 #, c-format msgid "Dimension array must be one dimensional." msgstr "次元配列は1次元でなければなりません" -#: utils/adt/arrayfuncs.c:5813 utils/adt/arrayfuncs.c:5839 +#: utils/adt/arrayfuncs.c:5862 utils/adt/arrayfuncs.c:5888 #, c-format msgid "dimension values cannot be null" msgstr "次元値にnullにはできません" -#: utils/adt/arrayfuncs.c:5845 +#: utils/adt/arrayfuncs.c:5894 #, c-format msgid "Low bound array has different size than dimensions array." msgstr "下限配列が次元配列のサイズと異なっています" -#: utils/adt/arrayfuncs.c:6123 +#: utils/adt/arrayfuncs.c:6172 #, c-format msgid "removing elements from multidimensional arrays is not supported" msgstr "多次元配列からの要素削除はサポートされません" -#: utils/adt/arrayfuncs.c:6400 +#: utils/adt/arrayfuncs.c:6449 #, c-format msgid "thresholds must be one-dimensional array" msgstr "閾値は1次元の配列でなければなりません" -#: utils/adt/arrayfuncs.c:6405 +#: utils/adt/arrayfuncs.c:6454 #, c-format msgid "thresholds array must not contain NULLs" msgstr "閾値配列にはNULL値を含めてはいけません" -#: utils/adt/arrayutils.c:140 +#: utils/adt/arrayutils.c:134 #, c-format msgid "array lower bound is too large: %d" msgstr "配列の下界が大きすぎます: %d" -#: utils/adt/arrayutils.c:240 +#: utils/adt/arrayutils.c:234 #, c-format msgid "typmod array must be type cstring[]" msgstr "typmod配列はcstring[]型でなければなりません" -#: utils/adt/arrayutils.c:245 +#: utils/adt/arrayutils.c:239 #, c-format msgid "typmod array must be one-dimensional" msgstr "typmod配列は1次元の配列でなければなりません" -#: utils/adt/arrayutils.c:250 +#: utils/adt/arrayutils.c:244 #, c-format msgid "typmod array must not contain nulls" msgstr "typmod配列にはNULL値を含めてはいけません" @@ -21379,7 +21375,7 @@ msgid "time zone \"%s\" not recognized" msgstr "タイムゾーン\"%s\"は不明です" -#: utils/adt/date.c:2888 utils/adt/timestamp.c:5141 utils/adt/timestamp.c:5394 +#: utils/adt/date.c:2889 utils/adt/timestamp.c:5141 utils/adt/timestamp.c:5394 #, c-format msgid "interval time zone \"%s\" must not include months or days" msgstr "intervalによるタイムゾーン\"%s\"には月または日を含めてはいけません" @@ -21409,7 +21405,7 @@ msgid "This time zone name appears in the configuration file for time zone abbreviation \"%s\"." msgstr "このタイムゾーンはタイムゾーン省略名\"%s\"の構成ファイルにあるようです。" -#: utils/adt/datum.c:89 utils/adt/datum.c:101 +#: utils/adt/datum.c:90 utils/adt/datum.c:102 #, c-format msgid "invalid Datum pointer" msgstr "不正なDatumポインタ" @@ -23148,7 +23144,7 @@ msgid "TIMESTAMP(%d)%s precision reduced to maximum allowed, %d" msgstr "TIMESTAMP(%d)%sの位取りを許容最大値%dまで減らしました" -#: utils/adt/timestamp.c:176 utils/adt/timestamp.c:434 utils/misc/guc.c:11975 +#: utils/adt/timestamp.c:176 utils/adt/timestamp.c:434 utils/misc/guc.c:11983 #, c-format msgid "timestamp out of range: \"%s\"" msgstr "timestampが範囲外です: \"%s\"" @@ -24141,127 +24137,127 @@ msgid "too many connections for role \"%s\"" msgstr "ロール\"%s\"からの接続が多すぎます" -#: utils/init/miscinit.c:796 +#: utils/init/miscinit.c:804 #, c-format msgid "permission denied to set session authorization" msgstr "set session authorization用の権限がありません" -#: utils/init/miscinit.c:879 +#: utils/init/miscinit.c:887 #, c-format msgid "invalid role OID: %u" msgstr "不正なロールID: %u" -#: utils/init/miscinit.c:933 +#: utils/init/miscinit.c:941 #, c-format msgid "database system is shut down" msgstr "データベースシステムはシャットダウンしました" -#: utils/init/miscinit.c:1020 +#: utils/init/miscinit.c:1028 #, c-format msgid "could not create lock file \"%s\": %m" msgstr "ロックファイル\"%s\"を作成できませんでした: %m" -#: utils/init/miscinit.c:1034 +#: utils/init/miscinit.c:1042 #, c-format msgid "could not open lock file \"%s\": %m" msgstr "ロックファイル\"%s\"をオープンできませんでした: %m" -#: utils/init/miscinit.c:1041 +#: utils/init/miscinit.c:1049 #, c-format msgid "could not read lock file \"%s\": %m" msgstr "ロックファイル\"%s\"を読み取れませんでした: %m" -#: utils/init/miscinit.c:1050 +#: utils/init/miscinit.c:1058 #, c-format msgid "lock file \"%s\" is empty" msgstr "ロックファイル\"%s\"が空です" -#: utils/init/miscinit.c:1051 +#: utils/init/miscinit.c:1059 #, c-format msgid "Either another server is starting, or the lock file is the remnant of a previous server startup crash." msgstr "他のサーバが稼働しているか、前回のサーバ起動失敗のためロックファイルが残っているかのいずれかです" -#: utils/init/miscinit.c:1095 +#: utils/init/miscinit.c:1103 #, c-format msgid "lock file \"%s\" already exists" msgstr "ロックファイル\"%s\"はすでに存在します" -#: utils/init/miscinit.c:1099 +#: utils/init/miscinit.c:1107 #, c-format msgid "Is another postgres (PID %d) running in data directory \"%s\"?" msgstr "他のpostgres(PID %d)がデータディレクトリ\"%s\"で稼動していませんか?" -#: utils/init/miscinit.c:1101 +#: utils/init/miscinit.c:1109 #, c-format msgid "Is another postmaster (PID %d) running in data directory \"%s\"?" msgstr "他のpostmaster(PID %d)がデータディレクトリ\"%s\"で稼動していませんか?" -#: utils/init/miscinit.c:1104 +#: utils/init/miscinit.c:1112 #, c-format msgid "Is another postgres (PID %d) using socket file \"%s\"?" msgstr "他のpostgres(PID %d)がソケットファイル\"%s\"を使用していませんか?" -#: utils/init/miscinit.c:1106 +#: utils/init/miscinit.c:1114 #, c-format msgid "Is another postmaster (PID %d) using socket file \"%s\"?" msgstr "他のpostmaster(PID %d)がソケットファイル\"%s\"を使用していませんか?" -#: utils/init/miscinit.c:1157 +#: utils/init/miscinit.c:1165 #, c-format msgid "could not remove old lock file \"%s\": %m" msgstr "古いロックファイル\"%s\"を削除できませんでした: %m" -#: utils/init/miscinit.c:1159 +#: utils/init/miscinit.c:1167 #, c-format msgid "The file seems accidentally left over, but it could not be removed. Please remove the file by hand and try again." msgstr "このファイルは偶然残ってしまったようですが、削除できませんでした。手作業でこれを削除し再実行してください。" -#: utils/init/miscinit.c:1196 utils/init/miscinit.c:1210 utils/init/miscinit.c:1221 +#: utils/init/miscinit.c:1204 utils/init/miscinit.c:1218 utils/init/miscinit.c:1229 #, c-format msgid "could not write lock file \"%s\": %m" msgstr "ロックファイル\"%s\"に書き出せませんでした: %m" -#: utils/init/miscinit.c:1332 utils/init/miscinit.c:1474 utils/misc/guc.c:10088 +#: utils/init/miscinit.c:1340 utils/init/miscinit.c:1482 utils/misc/guc.c:10096 #, c-format msgid "could not read from file \"%s\": %m" msgstr "ファイル\"%s\"から読み取れませんでした: %m" -#: utils/init/miscinit.c:1462 +#: utils/init/miscinit.c:1470 #, c-format msgid "could not open file \"%s\": %m; continuing anyway" msgstr "ファイル\"%s\"をオープンできませんでした: %m; とりあえず続けます" -#: utils/init/miscinit.c:1487 +#: utils/init/miscinit.c:1495 #, c-format msgid "lock file \"%s\" contains wrong PID: %ld instead of %ld" msgstr "ロックファイル\"%s\"が誤ったPIDをもっています: %ld、正しくは%ld" -#: utils/init/miscinit.c:1526 utils/init/miscinit.c:1542 +#: utils/init/miscinit.c:1534 utils/init/miscinit.c:1550 #, c-format msgid "\"%s\" is not a valid data directory" msgstr "\"%s\"は有効なデータディレクトリではありません" -#: utils/init/miscinit.c:1528 +#: utils/init/miscinit.c:1536 #, c-format msgid "File \"%s\" is missing." msgstr "ファイル\"%s\"が存在しません" -#: utils/init/miscinit.c:1544 +#: utils/init/miscinit.c:1552 #, c-format msgid "File \"%s\" does not contain valid data." msgstr "ファイル\"%s\"に有効なデータがありません。" -#: utils/init/miscinit.c:1546 +#: utils/init/miscinit.c:1554 #, c-format msgid "You might need to initdb." msgstr "initdbする必要があるかもしれません" -#: utils/init/miscinit.c:1554 +#: utils/init/miscinit.c:1562 #, c-format msgid "The data directory was initialized by PostgreSQL version %s, which is not compatible with this version %s." msgstr "データディレクトリはPostgreSQLバージョン%sで初期化されましたが、これはバージョン%sとは互換性がありません" -#: utils/init/miscinit.c:1621 +#: utils/init/miscinit.c:1629 #, c-format msgid "loaded library \"%s\"" msgstr "ライブラリ\"%s\"をロードしました" @@ -24817,7 +24813,7 @@ msgstr "強制的に更新をディスクに同期します。" #: utils/misc/guc.c:1186 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "サーバは、確実に更新が物理的にディスクに書き込まれるように複数の場所でfsync()システムコールを使用します。これにより、オペレーティングシステムやハードウェアがクラッシュした後でもデータベースクラスタは一貫した状態に復旧することができます。" #: utils/misc/guc.c:1197 @@ -26418,7 +26414,7 @@ msgid "cannot set parameters during a parallel operation" msgstr "並列処理中はパラメータの設定はできません" -#: utils/misc/guc.c:6992 utils/misc/guc.c:7772 utils/misc/guc.c:7825 utils/misc/guc.c:7876 utils/misc/guc.c:8209 utils/misc/guc.c:8976 utils/misc/guc.c:9248 utils/misc/guc.c:10921 +#: utils/misc/guc.c:6992 utils/misc/guc.c:7772 utils/misc/guc.c:7825 utils/misc/guc.c:7876 utils/misc/guc.c:8209 utils/misc/guc.c:8976 utils/misc/guc.c:9255 utils/misc/guc.c:10929 #, c-format msgid "unrecognized configuration parameter \"%s\"" msgstr "設定パラメータ\"%s\"は不明です" @@ -26433,7 +26429,7 @@ msgid "parameter \"%s\" cannot be changed now" msgstr "現在パラメータ\"%s\"を変更できません" -#: utils/misc/guc.c:7058 utils/misc/guc.c:7105 utils/misc/guc.c:10937 +#: utils/misc/guc.c:7058 utils/misc/guc.c:7105 utils/misc/guc.c:10945 #, c-format msgid "permission denied to set parameter \"%s\"" msgstr "パラメータ\"%s\"を設定する権限がありません" @@ -26448,7 +26444,7 @@ msgid "cannot set parameter \"%s\" within security-definer function" msgstr "セキュリティー定義用関数内でパラメーター\"%s\"を設定できません" -#: utils/misc/guc.c:7780 utils/misc/guc.c:7830 utils/misc/guc.c:9255 +#: utils/misc/guc.c:7780 utils/misc/guc.c:7830 utils/misc/guc.c:9262 #, c-format msgid "must be superuser or a member of pg_read_all_settings to examine \"%s\"" msgstr "\"%s\"の内容を見るにはスーパユーザまたはpg_read_all_settingsロールである必要があります" @@ -26488,87 +26484,87 @@ msgid "attempt to redefine parameter \"%s\"" msgstr "パラメータ\"%s\"を再定義しようとしています" -#: utils/misc/guc.c:10476 +#: utils/misc/guc.c:10484 #, c-format msgid "while setting parameter \"%s\" to \"%s\"" msgstr "パラメータ\"%s\"の\"%s\"への変更中" -#: utils/misc/guc.c:10544 +#: utils/misc/guc.c:10552 #, c-format msgid "parameter \"%s\" could not be set" msgstr "パラメータ\"%s\"を設定できません" -#: utils/misc/guc.c:10636 +#: utils/misc/guc.c:10644 #, c-format msgid "could not parse setting for parameter \"%s\"" msgstr "パラメータ\"%s\"の設定をパースできません" -#: utils/misc/guc.c:10999 utils/misc/guc.c:11033 +#: utils/misc/guc.c:11007 utils/misc/guc.c:11041 #, c-format msgid "invalid value for parameter \"%s\": %d" msgstr "パラメータ\"%s\"の値が無効です: %d" -#: utils/misc/guc.c:11067 +#: utils/misc/guc.c:11075 #, c-format msgid "invalid value for parameter \"%s\": %g" msgstr "パラメータ\"%s\"の値が無効です: %g" -#: utils/misc/guc.c:11354 +#: utils/misc/guc.c:11362 #, c-format msgid "\"temp_buffers\" cannot be changed after any temporary tables have been accessed in the session." msgstr "当該セッションで何らかの一時テーブルがアクセスされた後は \"temp_buffers\"を変更できません" -#: utils/misc/guc.c:11366 +#: utils/misc/guc.c:11374 #, c-format msgid "Bonjour is not supported by this build" msgstr "このビルドでは bonjour はサポートされていません" -#: utils/misc/guc.c:11379 +#: utils/misc/guc.c:11387 #, c-format msgid "SSL is not supported by this build" msgstr "このインストレーションではSSLはサポートされていません" -#: utils/misc/guc.c:11391 +#: utils/misc/guc.c:11399 #, c-format msgid "Cannot enable parameter when \"log_statement_stats\" is true." msgstr "\"log_statement_stats\"が真の場合、パラメータを有効にできません" -#: utils/misc/guc.c:11403 +#: utils/misc/guc.c:11411 #, c-format msgid "Cannot enable \"log_statement_stats\" when \"log_parser_stats\", \"log_planner_stats\", or \"log_executor_stats\" is true." msgstr "\"log_parser_stats\"、\"log_planner_stats\"、\"log_executor_stats\"のいずれかが真の場合は\"log_statement_stats\"を有効にできません" -#: utils/misc/guc.c:11633 +#: utils/misc/guc.c:11641 #, c-format msgid "effective_io_concurrency must be set to 0 on platforms that lack posix_fadvise()." msgstr "posix_fadvise() をもたないプラットフォームではeffective_io_concurrencyは0に設定する必要があります。" -#: utils/misc/guc.c:11646 +#: utils/misc/guc.c:11654 #, c-format msgid "maintenance_io_concurrency must be set to 0 on platforms that lack posix_fadvise()." msgstr "posix_fadvise() をもたないプラットフォームではmaintenance_io_concurrencyは0に設定する必要があります。" -#: utils/misc/guc.c:11762 +#: utils/misc/guc.c:11770 #, c-format msgid "invalid character" msgstr "不正な文字" -#: utils/misc/guc.c:11822 +#: utils/misc/guc.c:11830 #, c-format msgid "recovery_target_timeline is not a valid number." msgstr "recovery_target_timelineが妥当な数値ではありません。" -#: utils/misc/guc.c:11862 +#: utils/misc/guc.c:11870 #, c-format msgid "multiple recovery targets specified" msgstr "複数のリカバリ目標が指定されています" -#: utils/misc/guc.c:11863 +#: utils/misc/guc.c:11871 #, c-format msgid "At most one of recovery_target, recovery_target_lsn, recovery_target_name, recovery_target_time, recovery_target_xid may be set." msgstr " recovery_target, recovery_target_lsn, recovery_target_name, recovery_target_time, recovery_target_xid はこの中の1つまで設定可能です。" -#: utils/misc/guc.c:11871 +#: utils/misc/guc.c:11879 #, c-format msgid "The only allowed value is \"immediate\"." msgstr "\"immediate\"のみが指定可能です。" @@ -26583,7 +26579,7 @@ msgid "query-specified return tuple and function return type are not compatible" msgstr "問い合わせで指定された返却タプルと関数の返り値の型が互換ではありません" -#: utils/misc/pg_controldata.c:60 utils/misc/pg_controldata.c:138 utils/misc/pg_controldata.c:241 utils/misc/pg_controldata.c:306 +#: utils/misc/pg_controldata.c:63 utils/misc/pg_controldata.c:143 utils/misc/pg_controldata.c:248 utils/misc/pg_controldata.c:315 #, c-format msgid "calculated CRC checksum does not match value stored in file" msgstr "算出されたCRCチェックサムがファイルに格納されている値と一致しません" @@ -26827,3 +26823,6 @@ #, c-format msgid "cannot import a snapshot from a different database" msgstr "異なるデータベースからのスナップショットを読み込むことはできません" + +#~ msgid "record length %u at %X/%X too long" +#~ msgstr "%2$X/%3$Xのレコード長%1$uが大きすぎます" diff -Nru postgresql-13-13.13/src/backend/po/ko.po postgresql-13-13.14/src/backend/po/ko.po --- postgresql-13-13.13/src/backend/po/ko.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/ko.po 2024-02-05 21:47:02.000000000 +0000 @@ -26463,7 +26463,7 @@ #: utils/misc/guc.c:1185 msgid "" "The server will use the fsync() system call in several places to make sure " -"that updates are physically written to disk. This insures that a database " +"that updates are physically written to disk. This ensures that a database " "cluster will recover to a consistent state after an operating system or " "hardware crash." msgstr "" diff -Nru postgresql-13-13.13/src/backend/po/ru.po postgresql-13-13.14/src/backend/po/ru.po --- postgresql-13-13.13/src/backend/po/ru.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/ru.po 2024-02-05 21:47:02.000000000 +0000 @@ -27780,7 +27780,7 @@ #: utils/misc/guc.c:1186 msgid "" "The server will use the fsync() system call in several places to make sure " -"that updates are physically written to disk. This insures that a database " +"that updates are physically written to disk. This ensures that a database " "cluster will recover to a consistent state after an operating system or " "hardware crash." msgstr "" diff -Nru postgresql-13-13.13/src/backend/po/sv.po postgresql-13-13.14/src/backend/po/sv.po --- postgresql-13-13.13/src/backend/po/sv.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/sv.po 2024-02-05 21:47:02.000000000 +0000 @@ -25597,7 +25597,7 @@ msgstr "Tvingar synkronisering av uppdateringar till disk." #: utils/misc/guc.c:1186 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "Servern kommer använda systemanropet fsync() på ett antal platser för att se till att uppdateringar fysiskt skrivs till disk. Detta för att säkerställa att databasklustret kan starta i ett konsistent tillstånd efter en operativsystemkrash eller hårdvarukrash." #: utils/misc/guc.c:1197 diff -Nru postgresql-13-13.13/src/backend/po/tr.po postgresql-13-13.14/src/backend/po/tr.po --- postgresql-13-13.13/src/backend/po/tr.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/tr.po 2024-02-05 21:47:02.000000000 +0000 @@ -24247,7 +24247,7 @@ msgstr "Disk göncellemelerin anuyumlu olmasını zorluyor" #: utils/misc/guc.c:1125 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "Sunucu, güncellemelerin fiziksel olarak diske yazılmasına emin olmak için fsync() sistem fonksiyonunu kullanıyor. Bu, işletim sistemi veya donanımın çöküşünden sonra veritabanı cluster'in tutarlı bir duruma kurtarılmasını garantiliyor." #: utils/misc/guc.c:1136 diff -Nru postgresql-13-13.13/src/backend/po/uk.po postgresql-13-13.14/src/backend/po/uk.po --- postgresql-13-13.13/src/backend/po/uk.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/uk.po 2024-02-05 21:47:02.000000000 +0000 @@ -2,8 +2,8 @@ msgstr "" "Project-Id-Version: postgresql\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" -"POT-Creation-Date: 2023-08-16 15:24+0000\n" -"PO-Revision-Date: 2023-08-17 15:51\n" +"POT-Creation-Date: 2023-12-17 22:54+0000\n" +"PO-Revision-Date: 2023-12-18 17:41\n" "Last-Translator: \n" "Language-Team: Ukrainian\n" "Language: uk_UA\n" @@ -24,24 +24,24 @@ msgid "not recorded" msgstr "не записано" -#: ../common/controldata_utils.c:68 ../common/controldata_utils.c:73 -#: commands/copy.c:3499 commands/extension.c:3462 utils/adt/genfile.c:125 +#: ../common/controldata_utils.c:78 ../common/controldata_utils.c:83 +#: commands/copy.c:3503 commands/extension.c:3462 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 +#: ../common/controldata_utils.c:96 ../common/controldata_utils.c:99 #: 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/twophase.c:1334 access/transam/xlog.c:3530 +#: access/transam/xlog.c:4774 access/transam/xlog.c:11420 +#: access/transam/xlog.c:11433 access/transam/xlog.c:11888 +#: access/transam/xlog.c:11968 access/transam/xlog.c:12007 +#: access/transam/xlog.c:12050 access/transam/xlogfuncs.c:662 #: access/transam/xlogfuncs.c:681 commands/extension.c:3472 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/logical/snapbuild.c:1874 replication/logical/snapbuild.c:1916 +#: replication/logical/snapbuild.c:1944 replication/logical/snapbuild.c:1971 #: 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 @@ -49,31 +49,31 @@ msgid "could not read file \"%s\": %m" msgstr "не вдалося прочитати файл \"%s\": %m" -#: ../common/controldata_utils.c:97 ../common/controldata_utils.c:101 -#: access/transam/twophase.c:1337 access/transam/xlog.c:3533 -#: access/transam/xlog.c:4777 replication/logical/origin.c:722 -#: replication/logical/origin.c:761 replication/logical/snapbuild.c:1867 -#: replication/logical/snapbuild.c:1909 replication/logical/snapbuild.c:1937 -#: replication/logical/snapbuild.c:1964 replication/slot.c:1720 +#: ../common/controldata_utils.c:107 ../common/controldata_utils.c:111 +#: access/transam/twophase.c:1337 access/transam/xlog.c:3535 +#: access/transam/xlog.c:4779 replication/logical/origin.c:722 +#: replication/logical/origin.c:761 replication/logical/snapbuild.c:1879 +#: replication/logical/snapbuild.c:1921 replication/logical/snapbuild.c:1949 +#: replication/logical/snapbuild.c:1976 replication/slot.c:1720 #: replication/slot.c:1761 replication/walsender.c:553 #: utils/cache/relmapper.c:748 #, c-format msgid "could not read file \"%s\": read %d of %zu" msgstr "не вдалося прочитати файл \"%s\": прочитано %d з %zu" -#: ../common/controldata_utils.c:112 ../common/controldata_utils.c:117 -#: ../common/controldata_utils.c:256 ../common/controldata_utils.c:259 +#: ../common/controldata_utils.c:122 ../common/controldata_utils.c:127 +#: ../common/controldata_utils.c:286 ../common/controldata_utils.c:289 #: access/heap/rewriteheap.c:1178 access/heap/rewriteheap.c:1281 #: access/transam/timeline.c:392 access/transam/timeline.c:438 #: access/transam/timeline.c:516 access/transam/twophase.c:1346 -#: access/transam/twophase.c:1757 access/transam/xlog.c:3397 -#: access/transam/xlog.c:3568 access/transam/xlog.c:3573 -#: access/transam/xlog.c:3901 access/transam/xlog.c:4742 -#: access/transam/xlog.c:5666 access/transam/xlogfuncs.c:687 +#: access/transam/twophase.c:1757 access/transam/xlog.c:3399 +#: access/transam/xlog.c:3570 access/transam/xlog.c:3575 +#: access/transam/xlog.c:3903 access/transam/xlog.c:4744 +#: access/transam/xlog.c:5668 access/transam/xlogfuncs.c:687 #: commands/copy.c:1813 libpq/be-fsstubs.c:455 libpq/be-fsstubs.c:525 #: replication/logical/origin.c:655 replication/logical/origin.c:794 #: replication/logical/reorderbuffer.c:3719 -#: replication/logical/snapbuild.c:1771 replication/logical/snapbuild.c:1972 +#: replication/logical/snapbuild.c:1783 replication/logical/snapbuild.c:1984 #: replication/slot.c:1607 replication/slot.c:1768 replication/walsender.c:563 #: storage/file/copydir.c:218 storage/file/copydir.c:223 storage/file/fd.c:704 #: storage/file/fd.c:3445 storage/file/fd.c:3548 utils/cache/relmapper.c:759 @@ -82,11 +82,11 @@ msgid "could not close file \"%s\": %m" msgstr "неможливо закрити файл \"%s\": %m" -#: ../common/controldata_utils.c:135 +#: ../common/controldata_utils.c:165 msgid "byte ordering mismatch" msgstr "неправильний порядок байтів" -#: ../common/controldata_utils.c:137 +#: ../common/controldata_utils.c:167 #, c-format msgid "possible byte ordering mismatch\n" "The byte ordering used to store the pg_control file might not match the one\n" @@ -95,50 +95,50 @@ msgstr "можлива помилка у послідовності байтів.\n" "Порядок байтів, що використовують для зберігання файлу pg_control, може не відповідати тому, який використовується цією програмою. У такому випадку результати нижче будуть неправильним, і інсталяція PostgreSQL буде несумісною з цим каталогом даних." -#: ../common/controldata_utils.c:197 ../common/controldata_utils.c:203 +#: ../common/controldata_utils.c:227 ../common/controldata_utils.c:233 #: ../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 +#: access/transam/xlog.c:3301 access/transam/xlog.c:3441 +#: access/transam/xlog.c:3485 access/transam/xlog.c:3683 +#: access/transam/xlog.c:3768 access/transam/xlog.c:3871 +#: access/transam/xlog.c:4764 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/logical/snapbuild.c:1738 replication/logical/snapbuild.c:1845 #: 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 +#: utils/init/miscinit.c:1329 utils/init/miscinit.c:1463 +#: utils/init/miscinit.c:1540 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 +#: ../common/controldata_utils.c:251 ../common/controldata_utils.c:254 #: 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 +#: access/transam/xlog.c:11177 access/transam/xlog.c:11215 +#: access/transam/xlog.c:11628 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/controldata_utils.c:269 ../common/controldata_utils.c:275 #: ../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 +#: access/transam/xlog.c:3392 access/transam/xlog.c:3564 +#: access/transam/xlog.c:4737 access/transam/xlog.c:10665 +#: access/transam/xlog.c:10692 replication/logical/snapbuild.c:1776 #: 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 @@ -171,7 +171,7 @@ msgid "could not change directory to \"%s\": %m" msgstr "не вдалося змінити каталог на \"%s\": %m" -#: ../common/exec.c:300 access/transam/xlog.c:11047 +#: ../common/exec.c:300 access/transam/xlog.c:11049 #: replication/basebackup.c:1424 utils/adt/misc.c:366 #, c-format msgid "could not read symbolic link \"%s\": %m" @@ -185,17 +185,17 @@ #: ../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 +#: access/transam/xlog.c:6547 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 +#: postmaster/postmaster.c:2553 postmaster/postmaster.c:4190 +#: postmaster/postmaster.c:5641 postmaster/postmaster.c:6001 #: 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 +#: 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 @@ -229,14 +229,14 @@ msgstr "неможливо дублювати нульовий покажчик (внутрішня помилка)\n" #: ../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/twophase.c:1302 access/transam/xlog.c:8106 +#: access/transam/xlog.c:11036 access/transam/xlog.c:11153 +#: access/transam/xlog.c:11191 access/transam/xlog.c:11408 #: access/transam/xlogarchive.c:110 access/transam/xlogarchive.c:226 -#: commands/copy.c:1941 commands/copy.c:3509 commands/extension.c:3451 +#: commands/copy.c:1941 commands/copy.c:3513 commands/extension.c:3451 #: commands/tablespace.c:806 commands/tablespace.c:897 #: replication/basebackup.c:444 replication/basebackup.c:627 -#: replication/basebackup.c:700 replication/logical/snapbuild.c:1640 +#: replication/basebackup.c:700 replication/logical/snapbuild.c:1652 #: 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 @@ -247,7 +247,7 @@ msgstr "не вдалося отримати інформацію від файлу \"%s\": %m" #: ../common/file_utils.c:158 ../common/pgfnames.c:48 commands/tablespace.c:729 -#: commands/tablespace.c:739 postmaster/postmaster.c:1509 +#: commands/tablespace.c:739 postmaster/postmaster.c:1512 #: storage/file/fd.c:2693 storage/file/reinit.c:122 utils/adt/misc.c:260 #: utils/misc/tzparser.c:338 #, c-format @@ -260,7 +260,7 @@ msgstr "не вдалося прочитати каталог \"%s\": %m" #: ../common/file_utils.c:375 access/transam/xlogarchive.c:411 -#: postmaster/syslogger.c:1523 replication/logical/snapbuild.c:1783 +#: postmaster/syslogger.c:1523 replication/logical/snapbuild.c:1795 #: replication/slot.c:650 replication/slot.c:1479 replication/slot.c:1621 #: storage/file/fd.c:714 storage/file/fd.c:815 utils/time/snapmgr.c:1379 #, c-format @@ -575,8 +575,8 @@ msgid "request for BRIN range summarization for index \"%s\" page %u was not recorded" msgstr "запит на підсумок діапазону BRIN для індексу «%s» сторінки %u не вдалося записати" -#: 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/brin/brin.c:962 access/brin/brin.c:1072 access/gin/ginfast.c:1042 +#: access/transam/xlog.c:10801 access/transam/xlog.c:11359 #: 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 @@ -585,29 +585,35 @@ msgid "recovery is in progress" msgstr "відновлення у процесі" -#: access/brin/brin.c:963 access/brin/brin.c:1067 +#: access/brin/brin.c:963 access/brin/brin.c:1073 #, c-format msgid "BRIN control functions cannot be executed during recovery." msgstr "Контрольна функція BRIN не може бути виконана під час відновлення." -#: access/brin/brin.c:971 access/brin/brin.c:1075 +#: access/brin/brin.c:971 access/brin/brin.c:1081 #, c-format msgid "block number out of range: %s" msgstr "заблоковане число за межами діапазону: %s" -#: access/brin/brin.c:1015 access/brin/brin.c:1101 +#: access/brin/brin.c:1015 access/brin/brin.c:1107 #, c-format msgid "\"%s\" is not a BRIN index" msgstr "\"%s\" не є індексом BRIN" -#: access/brin/brin.c:1031 access/brin/brin.c:1117 +#: access/brin/brin.c:1031 access/brin/brin.c:1123 #, c-format msgid "could not open parent table of index %s" msgstr "не вдалося відкрити батьківську таблицю індексу %s" +#: access/brin/brin.c:1040 access/brin/brin.c:1139 access/gin/ginfast.c:1087 +#: parser/parse_utilcmd.c:2243 +#, c-format +msgid "index \"%s\" is not valid" +msgstr "індекс \"%s\" не є припустимим" + #: access/brin/brin_pageops.c:76 access/brin/brin_pageops.c:362 #: access/brin/brin_pageops.c:848 access/gin/ginentrypage.c:110 -#: access/gist/gist.c:1438 access/spgist/spgdoinsert.c:1962 +#: access/gist/gist.c:1458 access/spgist/spgdoinsert.c:1962 #: access/spgist/spgdoinsert.c:2230 #, c-format msgid "index row size %zu exceeds maximum %zu for index \"%s\"" @@ -706,7 +712,7 @@ msgid "Attribute \"%s\" of type %s does not exist in type %s." msgstr "Атрибут \"%s\" типу %s не існує в типі %s." -#: access/common/heaptuple.c:1036 access/common/heaptuple.c:1371 +#: access/common/heaptuple.c:1133 access/common/heaptuple.c:1468 #, c-format msgid "number of columns (%d) exceeds limit (%d)" msgstr "кількість стовпців (%d) перевищує обмеження (%d)" @@ -750,7 +756,7 @@ msgid "unrecognized parameter namespace \"%s\"" msgstr "нерозпізнаний параметр простору імен \"%s\"" -#: access/common/reloptions.c:1277 utils/misc/guc.c:12078 +#: access/common/reloptions.c:1277 utils/misc/guc.c:12086 #, c-format msgid "tables declared WITH OIDS are not supported" msgstr "таблиці, позначені WITH OIDS, не підтримуються" @@ -816,17 +822,17 @@ msgid "Reduce maintenance_work_mem." msgstr "Зменшіть maintenance_work_mem." -#: access/gin/ginfast.c:1044 +#: access/gin/ginfast.c:1043 #, c-format msgid "GIN pending list cannot be cleaned up during recovery." msgstr "Черга записів GIN не може бути очищена під час відновлення." -#: access/gin/ginfast.c:1051 +#: access/gin/ginfast.c:1050 #, c-format msgid "\"%s\" is not a GIN index" msgstr "\"%s\" не є індексом GIN" -#: access/gin/ginfast.c:1062 +#: access/gin/ginfast.c:1061 #, c-format msgid "cannot access temporary indexes of other sessions" msgstr "доступ до тимчасових індексів з інших сесій заблокований" @@ -847,7 +853,7 @@ msgstr "Щоб виправити це, зробіть REINDEX INDEX \"%s\"." #: access/gin/ginutil.c:144 executor/execExpr.c:1918 -#: utils/adt/arrayfuncs.c:3790 utils/adt/arrayfuncs.c:6424 +#: utils/adt/arrayfuncs.c:3839 utils/adt/arrayfuncs.c:6473 #: utils/adt/rowtypes.c:936 #, c-format msgid "could not identify a comparison function for type %s" @@ -923,7 +929,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:1935 commands/tablecmds.c:16444 commands/view.c:86 +#: commands/indexcmds.c:1911 commands/tablecmds.c:16454 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 @@ -994,18 +1000,18 @@ msgid "attempted to delete invisible tuple" msgstr "спроба видалити невидимий кортеж" -#: access/heap/heapam.c:2971 access/heap/heapam.c:5834 +#: access/heap/heapam.c:2976 access/heap/heapam.c:5841 #, c-format msgid "cannot update tuples during a parallel operation" msgstr "неможливо оновити кортежі під час паралельної операції" -#: access/heap/heapam.c:3112 +#: access/heap/heapam.c:3117 #, c-format msgid "attempted to update invisible tuple" msgstr "спроба оновити невидимий кортеж" -#: access/heap/heapam.c:4476 access/heap/heapam.c:4514 -#: access/heap/heapam.c:4780 access/heap/heapam_handler.c:455 +#: access/heap/heapam.c:4483 access/heap/heapam.c:4521 +#: access/heap/heapam.c:4787 access/heap/heapam_handler.c:455 #, c-format msgid "could not obtain lock on row in relation \"%s\"" msgstr "не вдалося отримати блокування у рядку стосовно \"%s\"" @@ -1027,10 +1033,10 @@ #: 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 +#: access/transam/xlog.c:3324 access/transam/xlog.c:3499 +#: access/transam/xlog.c:4716 access/transam/xlog.c:11168 +#: access/transam/xlog.c:11206 access/transam/xlog.c:11611 +#: access/transam/xlogfuncs.c:735 postmaster/postmaster.c:4653 #: 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 @@ -1044,15 +1050,15 @@ #: access/heap/rewriteheap.c:1159 access/transam/timeline.c:384 #: access/transam/timeline.c:424 access/transam/timeline.c:502 -#: access/transam/xlog.c:3378 access/transam/xlog.c:3553 -#: access/transam/xlog.c:4726 postmaster/postmaster.c:4660 -#: postmaster/postmaster.c:4670 replication/logical/origin.c:587 +#: access/transam/xlog.c:3380 access/transam/xlog.c:3555 +#: access/transam/xlog.c:4728 postmaster/postmaster.c:4663 +#: postmaster/postmaster.c:4673 replication/logical/origin.c:587 #: replication/logical/origin.c:629 replication/logical/origin.c:648 -#: replication/logical/snapbuild.c:1740 replication/slot.c:1575 +#: replication/logical/snapbuild.c:1752 replication/slot.c:1575 #: storage/file/buffile.c:502 storage/file/copydir.c:207 -#: utils/init/miscinit.c:1396 utils/init/miscinit.c:1407 -#: utils/init/miscinit.c:1415 utils/misc/guc.c:8036 utils/misc/guc.c:8067 -#: utils/misc/guc.c:9997 utils/misc/guc.c:10011 utils/time/snapmgr.c:1363 +#: utils/init/miscinit.c:1404 utils/init/miscinit.c:1415 +#: utils/init/miscinit.c:1423 utils/misc/guc.c:8036 utils/misc/guc.c:8067 +#: utils/misc/guc.c:10005 utils/misc/guc.c:10019 utils/time/snapmgr.c:1363 #: utils/time/snapmgr.c:1370 #, c-format msgid "could not write to file \"%s\": %m" @@ -1062,7 +1068,7 @@ #: 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/logical/snapbuild.c:1694 replication/logical/snapbuild.c:2139 #: 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 @@ -1178,8 +1184,8 @@ msgstr[2] "%u сторінок повністю порожні.\n" msgstr[3] "%u сторінок повністю порожні.\n" -#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3656 -#: commands/indexcmds.c:3674 +#: access/heap/vacuumlazy.c:1752 commands/indexcmds.c:3632 +#: commands/indexcmds.c:3650 #, c-format msgid "%s." msgstr "%s." @@ -1292,8 +1298,8 @@ msgstr "для методу доступу індекса \"%s\" не заданий обробник" #: 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 +#: commands/indexcmds.c:2640 commands/tablecmds.c:254 commands/tablecmds.c:278 +#: commands/tablecmds.c:16150 commands/tablecmds.c:17656 #, c-format msgid "\"%s\" is not an index" msgstr "\"%s\" не є індексом" @@ -1339,17 +1345,17 @@ msgid "This can be caused by an interrupted VACUUM in version 9.3 or older, before upgrade. Please REINDEX it." msgstr "Це могло статися через переривання VACUUM у версії 9.3 або старше перед оновленням. Будь ласка, виконайте REINDEX." -#: access/nbtree/nbtutils.c:2664 +#: access/nbtree/nbtutils.c:2679 #, c-format msgid "index row size %zu exceeds btree version %u maximum %zu for index \"%s\"" msgstr "розмір рядка індексу %zu перевищує максимальний розмір для версії %u btree %zu для індексу \"%s\"" -#: access/nbtree/nbtutils.c:2670 +#: access/nbtree/nbtutils.c:2685 #, c-format msgid "Index row references tuple (%u,%u) in relation \"%s\"." msgstr "Рядок індексу посилається на кортеж (%u,,%u) у відношенні \"%s\"." -#: access/nbtree/nbtutils.c:2674 +#: access/nbtree/nbtutils.c:2689 #, c-format msgid "Values larger than 1/3 of a buffer page cannot be indexed.\n" "Consider a function index of an MD5 hash of the value, or use full text indexing." @@ -1383,7 +1389,7 @@ msgstr "\"%s\" є індексом" #: access/table/table.c:54 access/table/table.c:83 access/table/table.c:116 -#: catalog/aclchk.c:1816 commands/tablecmds.c:12912 commands/tablecmds.c:16151 +#: catalog/aclchk.c:1816 commands/tablecmds.c:12912 commands/tablecmds.c:16159 #, c-format msgid "\"%s\" is a composite type" msgstr "\"%s\" це складений тип" @@ -1398,7 +1404,7 @@ msgid "%s cannot be empty." msgstr "%s не може бути пустим." -#: access/table/tableamapi.c:122 utils/misc/guc.c:12002 +#: access/table/tableamapi.c:122 utils/misc/guc.c:12010 #, c-format msgid "%s is too long (maximum %d characters)." msgstr "%s занадто довгий (максимум %d символів)." @@ -1797,7 +1803,7 @@ msgid "calculated CRC checksum does not match value stored in file \"%s\"" msgstr "обчислена контрольна сума CRC не відповідає значенню, збереженому у файлі \"%s\"" -#: access/transam/twophase.c:1405 access/transam/xlog.c:6546 +#: access/transam/twophase.c:1405 access/transam/xlog.c:6548 #, c-format msgid "Failed while allocating a WAL reading processor." msgstr "Не вдалося розмістити обробник журналу транзакцій." @@ -2034,190 +2040,190 @@ msgid "cannot have more than 2^32-1 subtransactions in a transaction" msgstr "в одній транзакції не може бути більше 2^32-1 підтранзакцій" -#: access/transam/xlog.c:2576 +#: access/transam/xlog.c:2578 #, c-format msgid "could not write to log file %s at offset %u, length %zu: %m" msgstr "не вдалося записати у файл журналу %s (зсув: %u, довжина: %zu): %m" -#: access/transam/xlog.c:2852 +#: access/transam/xlog.c:2854 #, c-format msgid "updated min recovery point to %X/%X on timeline %u" msgstr "мінімальна точка відновлення змінена на %X/%X на лінії часу %u" -#: access/transam/xlog.c:3441 storage/file/fd.c:805 storage/file/fd.c:818 +#: access/transam/xlog.c:3443 storage/file/fd.c:805 storage/file/fd.c:818 #, c-format msgid "This is known to fail occasionally during archive recovery, where it is harmless." msgstr "Відомо, що можливі помилки під час відновлення архіву, коли це не шкодить." -#: access/transam/xlog.c:3969 access/transam/xlogutils.c:802 +#: access/transam/xlog.c:3971 access/transam/xlogutils.c:802 #: replication/walsender.c:2546 #, c-format msgid "requested WAL segment %s has already been removed" msgstr "запитуваний сегмент WAL %s вже видалений" -#: access/transam/xlog.c:4212 +#: access/transam/xlog.c:4214 #, c-format msgid "recycled write-ahead log file \"%s\"" msgstr "файл випереджувального журналювання \"%s\" використовується повторно" -#: access/transam/xlog.c:4224 +#: access/transam/xlog.c:4226 #, c-format msgid "removing write-ahead log file \"%s\"" msgstr "файл випереджувального журналювання \"%s\" видаляється" -#: access/transam/xlog.c:4244 +#: access/transam/xlog.c:4246 #, c-format msgid "could not rename file \"%s\": %m" msgstr "не вдалося перейменувати файл \"%s\": %m" -#: access/transam/xlog.c:4286 access/transam/xlog.c:4296 +#: access/transam/xlog.c:4288 access/transam/xlog.c:4298 #, c-format msgid "required WAL directory \"%s\" does not exist" msgstr "необхідний каталог WAL \"%s\" не існує" -#: access/transam/xlog.c:4302 +#: access/transam/xlog.c:4304 #, c-format msgid "creating missing WAL directory \"%s\"" msgstr "створюється відсутній каталог WAL \"%s\"" -#: access/transam/xlog.c:4305 commands/dbcommands.c:2278 +#: access/transam/xlog.c:4307 commands/dbcommands.c:2278 #, c-format msgid "could not create missing directory \"%s\": %m" msgstr "не вдалося створити відстуній каталог \"%s\": %m" -#: access/transam/xlog.c:4427 +#: access/transam/xlog.c:4429 #, c-format msgid "unexpected timeline ID %u in log segment %s, offset %u" msgstr "неочіукваний ID лінії часу %u в сегменті журналу %s, зсув %u" -#: access/transam/xlog.c:4565 +#: access/transam/xlog.c:4567 #, c-format msgid "new timeline %u is not a child of database system timeline %u" msgstr "нова лінія часу %u не є дочірньою для лінії часу системи бази даних %u" -#: access/transam/xlog.c:4579 +#: access/transam/xlog.c:4581 #, c-format msgid "new timeline %u forked off current database system timeline %u before current recovery point %X/%X" msgstr "нова лінія часу %u відгалузилась від поточної лінії часу бази даних %u до поточної точки відновлення %X/%X" -#: access/transam/xlog.c:4598 +#: access/transam/xlog.c:4600 #, c-format msgid "new target timeline is %u" msgstr "нова цільова лінія часу %u" -#: access/transam/xlog.c:4634 +#: access/transam/xlog.c:4636 #, c-format msgid "could not generate secret authorization token" msgstr "не вдалося згенерувати секретний токен для авторизації" -#: access/transam/xlog.c:4793 access/transam/xlog.c:4802 -#: access/transam/xlog.c:4826 access/transam/xlog.c:4833 -#: access/transam/xlog.c:4840 access/transam/xlog.c:4845 -#: access/transam/xlog.c:4852 access/transam/xlog.c:4859 -#: access/transam/xlog.c:4866 access/transam/xlog.c:4873 -#: access/transam/xlog.c:4880 access/transam/xlog.c:4887 -#: access/transam/xlog.c:4896 access/transam/xlog.c:4903 -#: utils/init/miscinit.c:1553 +#: access/transam/xlog.c:4795 access/transam/xlog.c:4804 +#: access/transam/xlog.c:4828 access/transam/xlog.c:4835 +#: access/transam/xlog.c:4842 access/transam/xlog.c:4847 +#: access/transam/xlog.c:4854 access/transam/xlog.c:4861 +#: access/transam/xlog.c:4868 access/transam/xlog.c:4875 +#: access/transam/xlog.c:4882 access/transam/xlog.c:4889 +#: access/transam/xlog.c:4898 access/transam/xlog.c:4905 +#: utils/init/miscinit.c:1561 #, c-format msgid "database files are incompatible with server" msgstr "файли бази даних є несумісними з даним сервером" -#: access/transam/xlog.c:4794 +#: access/transam/xlog.c:4796 #, c-format msgid "The database cluster was initialized with PG_CONTROL_VERSION %d (0x%08x), but the server was compiled with PG_CONTROL_VERSION %d (0x%08x)." msgstr "Кластер бази даних було ініціалізовано з PG_CONTROL_VERSION %d (0x%08x), але сервер було скомпільовано з PG_CONTROL_VERSION %d (0x%08x)." -#: access/transam/xlog.c:4798 +#: access/transam/xlog.c:4800 #, c-format msgid "This could be a problem of mismatched byte ordering. It looks like you need to initdb." msgstr "Можливо, проблема викликана різним порядком байту. Здається, вам потрібно виконати команду \"initdb\"." -#: access/transam/xlog.c:4803 +#: access/transam/xlog.c:4805 #, c-format msgid "The database cluster was initialized with PG_CONTROL_VERSION %d, but the server was compiled with PG_CONTROL_VERSION %d." msgstr "Кластер баз даних був ініціалізований з PG_CONTROL_VERSION %d, але сервер скомпільований з PG_CONTROL_VERSION %d." -#: access/transam/xlog.c:4806 access/transam/xlog.c:4830 -#: access/transam/xlog.c:4837 access/transam/xlog.c:4842 +#: access/transam/xlog.c:4808 access/transam/xlog.c:4832 +#: access/transam/xlog.c:4839 access/transam/xlog.c:4844 #, c-format msgid "It looks like you need to initdb." msgstr "Здається, Вам треба виконати initdb." -#: access/transam/xlog.c:4817 +#: access/transam/xlog.c:4819 #, c-format msgid "incorrect checksum in control file" msgstr "помилка контрольної суми у файлі pg_control" -#: access/transam/xlog.c:4827 +#: access/transam/xlog.c:4829 #, c-format msgid "The database cluster was initialized with CATALOG_VERSION_NO %d, but the server was compiled with CATALOG_VERSION_NO %d." msgstr "Кластер бази даних було ініціалізовано з CATALOG_VERSION_NO %d, але сервер було скомпільовано з CATALOG_VERSION_NO %d." -#: access/transam/xlog.c:4834 +#: access/transam/xlog.c:4836 #, c-format msgid "The database cluster was initialized with MAXALIGN %d, but the server was compiled with MAXALIGN %d." msgstr "Кластер бази даних було ініціалізовано з MAXALIGN %d, але сервер було скомпільовано з MAXALIGN %d." -#: access/transam/xlog.c:4841 +#: access/transam/xlog.c:4843 #, c-format msgid "The database cluster appears to use a different floating-point number format than the server executable." msgstr "Здається, в кластері баз даних і в програмі сервера використовуються різні формати чисел з плаваючою точкою." -#: access/transam/xlog.c:4846 +#: access/transam/xlog.c:4848 #, c-format msgid "The database cluster was initialized with BLCKSZ %d, but the server was compiled with BLCKSZ %d." msgstr "Кластер бази даних було ініціалізовано з BLCKSZ %d, але сервер було скомпільовано з BLCKSZ %d." -#: access/transam/xlog.c:4849 access/transam/xlog.c:4856 -#: access/transam/xlog.c:4863 access/transam/xlog.c:4870 -#: access/transam/xlog.c:4877 access/transam/xlog.c:4884 -#: access/transam/xlog.c:4891 access/transam/xlog.c:4899 -#: access/transam/xlog.c:4906 +#: access/transam/xlog.c:4851 access/transam/xlog.c:4858 +#: access/transam/xlog.c:4865 access/transam/xlog.c:4872 +#: access/transam/xlog.c:4879 access/transam/xlog.c:4886 +#: access/transam/xlog.c:4893 access/transam/xlog.c:4901 +#: access/transam/xlog.c:4908 #, c-format msgid "It looks like you need to recompile or initdb." msgstr "Здається, вам потрібно перекомпілювати сервер або виконати initdb." -#: access/transam/xlog.c:4853 +#: access/transam/xlog.c:4855 #, c-format msgid "The database cluster was initialized with RELSEG_SIZE %d, but the server was compiled with RELSEG_SIZE %d." msgstr "Кластер бази даних було ініціалізовано з ELSEG_SIZE %d, але сервер було скомпільовано з ELSEG_SIZE %d." -#: access/transam/xlog.c:4860 +#: access/transam/xlog.c:4862 #, c-format msgid "The database cluster was initialized with XLOG_BLCKSZ %d, but the server was compiled with XLOG_BLCKSZ %d." msgstr "Кластер бази даних було ініціалізовано з XLOG_BLCKSZ %d, але сервер було скомпільовано з XLOG_BLCKSZ %d." -#: access/transam/xlog.c:4867 +#: access/transam/xlog.c:4869 #, c-format msgid "The database cluster was initialized with NAMEDATALEN %d, but the server was compiled with NAMEDATALEN %d." msgstr "Кластер бази даних було ініціалізовано з NAMEDATALEN %d, але сервер було скомпільовано з NAMEDATALEN %d." -#: access/transam/xlog.c:4874 +#: access/transam/xlog.c:4876 #, c-format msgid "The database cluster was initialized with INDEX_MAX_KEYS %d, but the server was compiled with INDEX_MAX_KEYS %d." msgstr "Кластер бази даних було ініціалізовано з INDEX_MAX_KEYS %d, але сервер було скомпільовано з INDEX_MAX_KEYS %d." -#: access/transam/xlog.c:4881 +#: access/transam/xlog.c:4883 #, c-format msgid "The database cluster was initialized with TOAST_MAX_CHUNK_SIZE %d, but the server was compiled with TOAST_MAX_CHUNK_SIZE %d." msgstr "Кластер бази даних було ініціалізовано з TOAST_MAX_CHUNK_SIZE %d, але сервер було скомпільовано з TOAST_MAX_CHUNK_SIZE %d." -#: access/transam/xlog.c:4888 +#: access/transam/xlog.c:4890 #, c-format msgid "The database cluster was initialized with LOBLKSIZE %d, but the server was compiled with LOBLKSIZE %d." msgstr "Кластер бази даних було ініціалізовано з LOBLKSIZE %d, але сервер було скомпільовано з LOBLKSIZE %d." -#: access/transam/xlog.c:4897 +#: access/transam/xlog.c:4899 #, c-format msgid "The database cluster was initialized without USE_FLOAT8_BYVAL but the server was compiled with USE_FLOAT8_BYVAL." msgstr "Кластер бази даних було ініціалізовано без USE_FLOAT8_BYVAL, але сервер було скомпільовано з USE_FLOAT8_BYVAL." -#: access/transam/xlog.c:4904 +#: access/transam/xlog.c:4906 #, c-format msgid "The database cluster was initialized with USE_FLOAT8_BYVAL but the server was compiled without USE_FLOAT8_BYVAL." msgstr "Кластер бази даних було ініціалізовано з USE_FLOAT8_BYVAL, але сервер було скомпільовано без USE_FLOAT8_BYVAL." -#: access/transam/xlog.c:4913 +#: access/transam/xlog.c:4915 #, c-format msgid "WAL segment size must be a power of two between 1 MB and 1 GB, but the control file specifies %d byte" msgid_plural "WAL segment size must be a power of two between 1 MB and 1 GB, but the control file specifies %d bytes" @@ -2226,247 +2232,247 @@ msgstr[2] "Розмір сегменту WAL повинен задаватись ступенем 2 в інтервалі від 1 МБ до 1 ГБ, але в керуючому файлі вказано значення %d" msgstr[3] "Розмір сегменту WAL повинен задаватись ступенем 2 в інтервалі від 1 МБ до 1 ГБ, але в керуючому файлі вказано значення %d" -#: access/transam/xlog.c:4925 +#: access/transam/xlog.c:4927 #, c-format msgid "\"min_wal_size\" must be at least twice \"wal_segment_size\"" msgstr "\"min_wal_size\" має бути мінімум у 2 рази більше, ніж \"wal_segment_size\"" -#: access/transam/xlog.c:4929 +#: access/transam/xlog.c:4931 #, c-format msgid "\"max_wal_size\" must be at least twice \"wal_segment_size\"" msgstr "\"max_wal_size\" має бути мінімум у 2 рази більше, ніж \"wal_segment_size\"" -#: access/transam/xlog.c:5362 +#: access/transam/xlog.c:5364 #, c-format msgid "could not write bootstrap write-ahead log file: %m" msgstr "не вдалося записати початкове завантаження випереджувального журналювання: %m" -#: access/transam/xlog.c:5370 +#: access/transam/xlog.c:5372 #, c-format msgid "could not fsync bootstrap write-ahead log file: %m" msgstr "не вдалося скинути на диск початкове завантаження випереджувального журналювання: %m" -#: access/transam/xlog.c:5376 +#: access/transam/xlog.c:5378 #, c-format msgid "could not close bootstrap write-ahead log file: %m" msgstr "не вдалося закрити початкове завантаження випереджувального журналювання: %m" -#: access/transam/xlog.c:5437 +#: access/transam/xlog.c:5439 #, c-format msgid "using recovery command file \"%s\" is not supported" msgstr "використання файлу команд відновлення \"%s\" не підтримується" -#: access/transam/xlog.c:5502 +#: access/transam/xlog.c:5504 #, c-format msgid "standby mode is not supported by single-user servers" msgstr "режим очікування не підтримується однокористувацьким сервером" -#: access/transam/xlog.c:5519 +#: access/transam/xlog.c:5521 #, c-format msgid "specified neither primary_conninfo nor restore_command" msgstr "не заззначено ані параметр primary_conninfo, ані параметр restore_command" -#: access/transam/xlog.c:5520 +#: access/transam/xlog.c:5522 #, c-format msgid "The database server will regularly poll the pg_wal subdirectory to check for files placed there." msgstr "Сервер бази даних буде регулярно опитувати підкатолог pg_wal і перевіряти файли, що містяться у ньому." -#: access/transam/xlog.c:5528 +#: access/transam/xlog.c:5530 #, c-format msgid "must specify restore_command when standby mode is not enabled" msgstr "необхідно вказати restore_command, якщо не ввімкнено режиму очікування" -#: access/transam/xlog.c:5566 +#: access/transam/xlog.c:5568 #, c-format msgid "recovery target timeline %u does not exist" msgstr "цільова лінія часу відновлення %u не існує" -#: access/transam/xlog.c:5688 +#: access/transam/xlog.c:5690 #, c-format msgid "archive recovery complete" msgstr "відновлення архіву завершено" -#: access/transam/xlog.c:5754 access/transam/xlog.c:6032 +#: access/transam/xlog.c:5756 access/transam/xlog.c:6034 #, c-format msgid "recovery stopping after reaching consistency" msgstr "відновлення зупиняється після досягнення узгодженості" -#: access/transam/xlog.c:5775 +#: access/transam/xlog.c:5777 #, c-format msgid "recovery stopping before WAL location (LSN) \"%X/%X\"" msgstr "відновлення зупиняється перед позицією WAL (LSN) \"%X/%X\"" -#: access/transam/xlog.c:5866 +#: access/transam/xlog.c:5868 #, c-format msgid "recovery stopping before commit of transaction %u, time %s" msgstr "відновлення припиняється до підтвердження транзакції %u, час %s" -#: access/transam/xlog.c:5873 +#: access/transam/xlog.c:5875 #, c-format msgid "recovery stopping before abort of transaction %u, time %s" msgstr "відновлення припиняється до скасування транзакції %u, час %s" -#: access/transam/xlog.c:5926 +#: access/transam/xlog.c:5928 #, c-format msgid "recovery stopping at restore point \"%s\", time %s" msgstr "відновлення припиняється в точці відновлення\"%s\", час %s" -#: access/transam/xlog.c:5944 +#: access/transam/xlog.c:5946 #, c-format msgid "recovery stopping after WAL location (LSN) \"%X/%X\"" msgstr "відновлення припиняється пісня локації WAL (LSN) \"%X/%X\"" -#: access/transam/xlog.c:6012 +#: access/transam/xlog.c:6014 #, c-format msgid "recovery stopping after commit of transaction %u, time %s" msgstr "відновлення припиняється після підтвердження транзакції %u, час %s" -#: access/transam/xlog.c:6020 +#: access/transam/xlog.c:6022 #, c-format msgid "recovery stopping after abort of transaction %u, time %s" msgstr "відновлення припиняється після скасування транзакції %u, час %s" -#: access/transam/xlog.c:6069 +#: access/transam/xlog.c:6071 #, c-format msgid "pausing at the end of recovery" msgstr "пауза в кінці відновлення" -#: access/transam/xlog.c:6070 +#: access/transam/xlog.c:6072 #, c-format msgid "Execute pg_wal_replay_resume() to promote." msgstr "Виконайте pg_wal_replay_resume() для підвищення рівня." -#: access/transam/xlog.c:6073 +#: access/transam/xlog.c:6075 #, c-format msgid "recovery has paused" msgstr "відновлення зупинено" -#: access/transam/xlog.c:6074 +#: access/transam/xlog.c:6076 #, c-format msgid "Execute pg_wal_replay_resume() to continue." msgstr "Виконайте pg_wal_replay_resume(), щоб продовжити." -#: access/transam/xlog.c:6294 +#: access/transam/xlog.c:6296 #, c-format msgid "hot standby is not possible because %s = %d is a lower setting than on the master server (its value was %d)" msgstr "hot standby неможливий, так як параметр %s = %d менший, ніж на головному сервері (його значення було %d)" -#: access/transam/xlog.c:6318 +#: access/transam/xlog.c:6320 #, c-format msgid "WAL was generated with wal_level=minimal, data may be missing" msgstr "WAL був створений з параметром wal_level=minimal, можлива втрата даних" -#: access/transam/xlog.c:6319 +#: access/transam/xlog.c:6321 #, c-format msgid "This happens if you temporarily set wal_level=minimal without taking a new base backup." msgstr "Це трапляється, якщо ви тимчасово встановили wal_level=minimal і не зробили резервну копію бази даних." -#: access/transam/xlog.c:6330 +#: access/transam/xlog.c:6332 #, c-format msgid "hot standby is not possible because wal_level was not set to \"replica\" or higher on the master server" msgstr "hot standby неможливий, так як на головному сервері встановлений невідповідний wal_level (повинен бути \"replica\" або вище)" -#: access/transam/xlog.c:6331 +#: access/transam/xlog.c:6333 #, c-format msgid "Either set wal_level to \"replica\" on the master, or turn off hot_standby here." msgstr "Або встановіть для wal_level значення \"replica\" на головному сервері, або вимкніть hot_standby тут." -#: access/transam/xlog.c:6393 +#: access/transam/xlog.c:6395 #, c-format msgid "control file contains invalid checkpoint location" msgstr "контрольний файл містить недійсне розташування контрольної точки" -#: access/transam/xlog.c:6404 +#: access/transam/xlog.c:6406 #, c-format msgid "database system was shut down at %s" msgstr "система бази даних була вимкнена %s" -#: access/transam/xlog.c:6410 +#: access/transam/xlog.c:6412 #, c-format msgid "database system was shut down in recovery at %s" msgstr "система бази даних завершила роботу у процесі відновлення %s" -#: access/transam/xlog.c:6416 +#: access/transam/xlog.c:6418 #, c-format msgid "database system shutdown was interrupted; last known up at %s" msgstr "завершення роботи бази даних було перервано; останній момент роботи %s" -#: access/transam/xlog.c:6422 +#: access/transam/xlog.c:6424 #, c-format msgid "database system was interrupted while in recovery at %s" msgstr "система бази даних була перервана в процесі відновлення %s" -#: access/transam/xlog.c:6424 +#: access/transam/xlog.c:6426 #, c-format msgid "This probably means that some data is corrupted and you will have to use the last backup for recovery." msgstr "Це, ймовірно, означає, що деякі дані були пошкоджені, і вам доведеться відновити базу даних з останнього збереження." -#: access/transam/xlog.c:6430 +#: access/transam/xlog.c:6432 #, c-format msgid "database system was interrupted while in recovery at log time %s" msgstr "робота системи бази даних була перервана в процесі відновлення, час в журналі %s" -#: access/transam/xlog.c:6432 +#: access/transam/xlog.c:6434 #, c-format msgid "If this has occurred more than once some data might be corrupted and you might need to choose an earlier recovery target." msgstr "Якщо це відбувається більше, ніж один раз, можливо, якісь дані були зіпсовані, і для відновлення треба вибрати більш ранню точку." -#: access/transam/xlog.c:6438 +#: access/transam/xlog.c:6440 #, c-format msgid "database system was interrupted; last known up at %s" msgstr "робота системи бази даних була перервана; останній момент роботи %s" -#: access/transam/xlog.c:6444 +#: access/transam/xlog.c:6446 #, c-format msgid "control file contains invalid database cluster state" msgstr "контрольний файл містить недійсний стан кластеру бази даних" -#: access/transam/xlog.c:6501 +#: access/transam/xlog.c:6503 #, c-format msgid "entering standby mode" msgstr "перехід у режим очікування" -#: access/transam/xlog.c:6504 +#: access/transam/xlog.c:6506 #, c-format msgid "starting point-in-time recovery to XID %u" msgstr "починається відновлення точки в часі до XID %u" -#: access/transam/xlog.c:6508 +#: access/transam/xlog.c:6510 #, c-format msgid "starting point-in-time recovery to %s" msgstr "починається відновлення точки в часі до %s" -#: access/transam/xlog.c:6512 +#: access/transam/xlog.c:6514 #, c-format msgid "starting point-in-time recovery to \"%s\"" msgstr "починається відновлення точки в часі до \"%s\"" -#: access/transam/xlog.c:6516 +#: access/transam/xlog.c:6518 #, c-format msgid "starting point-in-time recovery to WAL location (LSN) \"%X/%X\"" msgstr "починається відновлення точки в часі до локації WAL (LSN) \"%X/%X\"" -#: access/transam/xlog.c:6521 +#: access/transam/xlog.c:6523 #, c-format msgid "starting point-in-time recovery to earliest consistent point" msgstr "починається відновлення даних до першої точки домовленості" -#: access/transam/xlog.c:6524 +#: access/transam/xlog.c:6526 #, c-format msgid "starting archive recovery" msgstr "початок відновлення архіву" -#: access/transam/xlog.c:6583 access/transam/xlog.c:6716 +#: access/transam/xlog.c:6585 access/transam/xlog.c:6718 #, c-format msgid "checkpoint record is at %X/%X" msgstr "запис контрольної точки є на %X/%X" -#: access/transam/xlog.c:6598 +#: access/transam/xlog.c:6600 #, c-format msgid "could not find redo location referenced by checkpoint record" msgstr "не вдалося знайти положення REDO, вказане записом контрольної точки" -#: access/transam/xlog.c:6599 access/transam/xlog.c:6609 +#: access/transam/xlog.c:6601 access/transam/xlog.c:6611 #, c-format msgid "If you are restoring from a backup, touch \"%s/recovery.signal\" and add required recovery options.\n" "If you are not restoring from a backup, try removing the file \"%s/backup_label\".\n" @@ -2475,298 +2481,298 @@ "Якщо ви не відновлюєте з резервної копії, спробуйте видалити файл \"%s/backup_label\".\n" "Будьте обережні: видалення \"%s/backup_label\" призведе до пошкодження кластеру при відновленні з резервної копії." -#: access/transam/xlog.c:6608 +#: access/transam/xlog.c:6610 #, c-format msgid "could not locate required checkpoint record" msgstr "не вдалося знайти запис потрібної контрольної точки" -#: access/transam/xlog.c:6637 commands/tablespace.c:665 +#: access/transam/xlog.c:6639 commands/tablespace.c:665 #, c-format msgid "could not create symbolic link \"%s\": %m" msgstr "не вдалося створити символічне послання \"%s\": %m" -#: access/transam/xlog.c:6669 access/transam/xlog.c:6675 +#: access/transam/xlog.c:6671 access/transam/xlog.c:6677 #, c-format msgid "ignoring file \"%s\" because no file \"%s\" exists" msgstr "файл \"%s\" ігнорується, тому що файлу \"%s\" не існує" -#: access/transam/xlog.c:6671 access/transam/xlog.c:12127 +#: access/transam/xlog.c:6673 access/transam/xlog.c:12129 #, c-format msgid "File \"%s\" was renamed to \"%s\"." msgstr "Файл \"%s\" був перейменований на \"%s\"." -#: access/transam/xlog.c:6677 +#: access/transam/xlog.c:6679 #, c-format msgid "Could not rename file \"%s\" to \"%s\": %m." msgstr "Неможливо перейменувати файл \"%s\" на \"%s\": %m." -#: access/transam/xlog.c:6728 +#: access/transam/xlog.c:6730 #, c-format msgid "could not locate a valid checkpoint record" msgstr "не вдалося знайти запис допустимої контрольної точки" -#: access/transam/xlog.c:6766 +#: access/transam/xlog.c:6768 #, c-format msgid "requested timeline %u is not a child of this server's history" msgstr "запитувана лінія часу %u не є відгалуженням історії цього серверу" -#: access/transam/xlog.c:6768 +#: access/transam/xlog.c:6770 #, c-format msgid "Latest checkpoint is at %X/%X on timeline %u, but in the history of the requested timeline, the server forked off from that timeline at %X/%X." msgstr "Остання контрольна точка %X/%X на лінії часу %u, але в історії запитуваної лінії часу сервер відгалузився з цієї лінії в %X/%X." -#: access/transam/xlog.c:6784 +#: access/transam/xlog.c:6786 #, c-format msgid "requested timeline %u does not contain minimum recovery point %X/%X on timeline %u" msgstr "запитувана лінія часу %u не містить мінімальну точку відновлення %X/%X на лінії часу %u" -#: access/transam/xlog.c:6815 +#: access/transam/xlog.c:6817 #, c-format msgid "invalid next transaction ID" msgstr "невірний ID наступної транзакції" -#: access/transam/xlog.c:6909 +#: access/transam/xlog.c:6911 #, c-format msgid "invalid redo in checkpoint record" msgstr "невірний запис REDO в контрольній точці" -#: access/transam/xlog.c:6920 +#: access/transam/xlog.c:6922 #, c-format msgid "invalid redo record in shutdown checkpoint" msgstr "невірний запис REDO в контрольній точці вимкнення" -#: access/transam/xlog.c:6960 +#: access/transam/xlog.c:6962 #, c-format msgid "database system was not properly shut down; automatic recovery in progress" msgstr "робота системи бази даних не була завершена належним чином; відбувається автоматичне відновлення" -#: access/transam/xlog.c:6964 +#: access/transam/xlog.c:6966 #, c-format msgid "crash recovery starts in timeline %u and has target timeline %u" msgstr "відновлення після збою починається на лінії часу %u і має цільову лінію часу: %u" -#: access/transam/xlog.c:7011 +#: access/transam/xlog.c:7013 #, c-format msgid "backup_label contains data inconsistent with control file" msgstr "backup_label містить дані, які не узгоджені з файлом pg_control" -#: access/transam/xlog.c:7012 +#: access/transam/xlog.c:7014 #, c-format msgid "This means that the backup is corrupted and you will have to use another backup for recovery." msgstr "Це означає, що резервна копія була пошкоджена і вам доведеться використати іншу резервну копію для відновлення." -#: access/transam/xlog.c:7103 +#: access/transam/xlog.c:7105 #, c-format msgid "initializing for hot standby" msgstr "ініціалізація для hot standby" -#: access/transam/xlog.c:7236 +#: access/transam/xlog.c:7238 #, c-format msgid "redo starts at %X/%X" msgstr "запис REDO починається з %X/%X" -#: access/transam/xlog.c:7460 +#: access/transam/xlog.c:7462 #, c-format msgid "requested recovery stop point is before consistent recovery point" msgstr "запитувана точка відновлення передує узгодженій точці відновлення" -#: access/transam/xlog.c:7498 +#: access/transam/xlog.c:7500 #, c-format msgid "redo done at %X/%X" msgstr "записи REDO оброблені до %X/%X" -#: access/transam/xlog.c:7503 +#: access/transam/xlog.c:7505 #, c-format msgid "last completed transaction was at log time %s" msgstr "остання завершена транзакція була в %s" -#: access/transam/xlog.c:7512 +#: access/transam/xlog.c:7514 #, c-format msgid "redo is not required" msgstr "дані REDO не потрібні" -#: access/transam/xlog.c:7524 +#: access/transam/xlog.c:7526 #, c-format msgid "recovery ended before configured recovery target was reached" msgstr "відновлення завершилось до досягення налаштованої цілі відновлення" -#: access/transam/xlog.c:7608 access/transam/xlog.c:7612 +#: access/transam/xlog.c:7610 access/transam/xlog.c:7614 #, c-format msgid "WAL ends before end of online backup" msgstr "WAL завершився до завершення онлайн резервного копіювання" -#: access/transam/xlog.c:7609 +#: access/transam/xlog.c:7611 #, c-format msgid "All WAL generated while online backup was taken must be available at recovery." msgstr "Всі журнали WAL, створені під час резервного копіювання \"на ходу\", повинні бути в наявності для відновлення." -#: access/transam/xlog.c:7613 +#: access/transam/xlog.c:7615 #, c-format msgid "Online backup started with pg_start_backup() must be ended with pg_stop_backup(), and all WAL up to that point must be available at recovery." msgstr "Резервне копіювання БД \"на ходу\", розпочате за допомогою команди \"pg_start_backup()\", повинне завершуватися командою \"pg_stop_backup()\", і для відновлення повинні бути доступні усі журнали WAL. " -#: access/transam/xlog.c:7616 +#: access/transam/xlog.c:7618 #, c-format msgid "WAL ends before consistent recovery point" msgstr "WAL завершився до узгодженої точки відновлення" -#: access/transam/xlog.c:7651 +#: access/transam/xlog.c:7653 #, c-format msgid "selected new timeline ID: %u" msgstr "вибрано новий ID часової лінії: %u" -#: access/transam/xlog.c:8112 +#: access/transam/xlog.c:8114 #, c-format msgid "unexpected directory entry \"%s\" found in %s" msgstr "знайдено неочікуваний запис каталогу \"%s\" в %s" -#: access/transam/xlog.c:8114 +#: access/transam/xlog.c:8116 #, c-format msgid "All directory entries in pg_tblspc/ should be symbolic links." msgstr "Всі записи каталогу в pg_tblspc/ повинні бути символічними посиланнями." -#: access/transam/xlog.c:8115 +#: access/transam/xlog.c:8117 #, 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:8199 +#: access/transam/xlog.c:8201 #, c-format msgid "consistent recovery state reached at %X/%X" msgstr "узгоджений стан відновлення досягнутий %X/%X" -#: access/transam/xlog.c:8409 +#: access/transam/xlog.c:8411 #, c-format msgid "invalid primary checkpoint link in control file" msgstr "невірне посилання на первинну контрольну точку в контрольному файлі" -#: access/transam/xlog.c:8413 +#: access/transam/xlog.c:8415 #, c-format msgid "invalid checkpoint link in backup_label file" msgstr "невірне посилання на контрольну точку в файлі backup_label" -#: access/transam/xlog.c:8431 +#: access/transam/xlog.c:8433 #, c-format msgid "invalid primary checkpoint record" msgstr "невірний запис первинної контрольної точки" -#: access/transam/xlog.c:8435 +#: access/transam/xlog.c:8437 #, c-format msgid "invalid checkpoint record" msgstr "невірний запис контрольної точки" -#: access/transam/xlog.c:8446 +#: access/transam/xlog.c:8448 #, c-format msgid "invalid resource manager ID in primary checkpoint record" msgstr "невірний ID менеджера ресурсів в записі первинної контрольної точки" -#: access/transam/xlog.c:8450 +#: access/transam/xlog.c:8452 #, c-format msgid "invalid resource manager ID in checkpoint record" msgstr "невірний ID менеджера ресурсів в записі контрольної точки" -#: access/transam/xlog.c:8463 +#: access/transam/xlog.c:8465 #, c-format msgid "invalid xl_info in primary checkpoint record" msgstr "невірний xl_info у записі первинної контрольної точки" -#: access/transam/xlog.c:8467 +#: access/transam/xlog.c:8469 #, c-format msgid "invalid xl_info in checkpoint record" msgstr "невірний xl_info у записі контрольної точки" -#: access/transam/xlog.c:8478 +#: access/transam/xlog.c:8480 #, c-format msgid "invalid length of primary checkpoint record" msgstr "невірна довжина запису первинної контрольної очки" -#: access/transam/xlog.c:8482 +#: access/transam/xlog.c:8484 #, c-format msgid "invalid length of checkpoint record" msgstr "невірна довжина запису контрольної точки" -#: access/transam/xlog.c:8662 +#: access/transam/xlog.c:8664 #, c-format msgid "shutting down" msgstr "завершення роботи" -#: access/transam/xlog.c:8969 +#: access/transam/xlog.c:8971 #, c-format msgid "checkpoint skipped because system is idle" msgstr "контрольну точку пропущено, тому що система перебуває в режимі простоювання" -#: access/transam/xlog.c:9179 +#: access/transam/xlog.c:9181 #, c-format msgid "concurrent write-ahead log activity while database system is shutting down" msgstr "під час того вимкнення БД помічено конкурентну активність у випереджувальному журналюванні" -#: access/transam/xlog.c:9491 +#: access/transam/xlog.c:9493 #, c-format msgid "skipping restartpoint, recovery has already ended" msgstr "пропуск контрольної точки, відновлення вже завершено" -#: access/transam/xlog.c:9514 +#: access/transam/xlog.c:9516 #, c-format msgid "skipping restartpoint, already performed at %X/%X" msgstr "створення точки перезапуску пропускається, вона вже створена в %X/%X" -#: access/transam/xlog.c:9704 +#: access/transam/xlog.c:9706 #, c-format msgid "recovery restart point at %X/%X" msgstr "відновлення збереженої точки %X/%X" -#: access/transam/xlog.c:9706 +#: access/transam/xlog.c:9708 #, c-format msgid "Last completed transaction was at log time %s." msgstr "Остання завершена транзакція була в %s." -#: access/transam/xlog.c:9954 +#: access/transam/xlog.c:9956 #, c-format msgid "restore point \"%s\" created at %X/%X" msgstr "точка відновлення \"%s\" створена в %X/%X" -#: access/transam/xlog.c:10099 +#: access/transam/xlog.c:10101 #, c-format msgid "unexpected previous timeline ID %u (current timeline ID %u) in checkpoint record" msgstr "несподіваний ID попередньої лінії часу %u (ID теперішньої лінії часу %u) в записі контрольної точки" -#: access/transam/xlog.c:10108 +#: access/transam/xlog.c:10110 #, c-format msgid "unexpected timeline ID %u (after %u) in checkpoint record" msgstr "неочікуваний ID лінії часу %u (після %u) в записі контрольної точки" -#: access/transam/xlog.c:10124 +#: access/transam/xlog.c:10126 #, c-format msgid "unexpected timeline ID %u in checkpoint record, before reaching minimum recovery point %X/%X on timeline %u" msgstr "неочікуваний ID лінії часу %u в записі контрольної точки, до досягнення мінімальної точки відновлення %X/%X на лінії часу %u" -#: access/transam/xlog.c:10200 +#: access/transam/xlog.c:10202 #, c-format msgid "online backup was canceled, recovery cannot continue" msgstr "онлайн резервне копіювання скасовано, неможливо продовжити відновлення" -#: access/transam/xlog.c:10256 access/transam/xlog.c:10312 -#: access/transam/xlog.c:10342 +#: access/transam/xlog.c:10258 access/transam/xlog.c:10314 +#: access/transam/xlog.c:10344 #, c-format msgid "unexpected timeline ID %u (should be %u) in checkpoint record" msgstr "несподіваний ID лінії часу %u (повинен бути %u) в записі контрольної точки" -#: access/transam/xlog.c:10502 +#: access/transam/xlog.c:10504 #, c-format msgid "successfully skipped missing contrecord at %X/%X, overwritten at %s" msgstr "успішно пропущений відсутній contrecord при %X/%X, перезаписано на %s" -#: access/transam/xlog.c:10695 +#: access/transam/xlog.c:10697 #, c-format msgid "could not fsync write-through file \"%s\": %m" msgstr "не вдалосьясинхронізувати файл наскрізного запису %s: %m" -#: access/transam/xlog.c:10701 +#: access/transam/xlog.c:10703 #, c-format msgid "could not fdatasync file \"%s\": %m" msgstr "не вдалося fdatasync файл \"%s\": %m" -#: access/transam/xlog.c:10800 access/transam/xlog.c:11358 +#: access/transam/xlog.c:10802 access/transam/xlog.c:11360 #: 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 @@ -2774,201 +2780,201 @@ msgid "WAL control functions cannot be executed during recovery." msgstr "Функції управління WAL не можна використовувати під час відновлення." -#: access/transam/xlog.c:10809 access/transam/xlog.c:11367 +#: access/transam/xlog.c:10811 access/transam/xlog.c:11369 #, c-format msgid "WAL level not sufficient for making an online backup" msgstr "Обраний рівень WAL недостатній для резервного копіювання \"на ходу\"" -#: access/transam/xlog.c:10810 access/transam/xlog.c:11368 +#: access/transam/xlog.c:10812 access/transam/xlog.c:11370 #: 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:10815 +#: access/transam/xlog.c:10817 #, c-format msgid "backup label too long (max %d bytes)" msgstr "мітка резервного копіювання задовга (максимум %d байт)" -#: access/transam/xlog.c:10852 access/transam/xlog.c:11157 -#: access/transam/xlog.c:11195 +#: access/transam/xlog.c:10854 access/transam/xlog.c:11159 +#: access/transam/xlog.c:11197 #, c-format msgid "a backup is already in progress" msgstr "резервне копіювання вже триває" -#: access/transam/xlog.c:10853 +#: access/transam/xlog.c:10855 #, c-format msgid "Run pg_stop_backup() and try again." msgstr "Запустіть pg_stop_backup() і спробуйте знову." -#: access/transam/xlog.c:10949 +#: access/transam/xlog.c:10951 #, c-format msgid "WAL generated with full_page_writes=off was replayed since last restartpoint" msgstr "Після останньої точки відновлення був відтворений WAL, створений в режимі full_page_writes=off" -#: access/transam/xlog.c:10951 access/transam/xlog.c:11563 +#: access/transam/xlog.c:10953 access/transam/xlog.c:11565 #, 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:11054 replication/basebackup.c:1429 +#: access/transam/xlog.c:11056 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:11107 commands/tablespace.c:385 +#: access/transam/xlog.c:11109 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:11158 access/transam/xlog.c:11196 +#: access/transam/xlog.c:11160 access/transam/xlog.c:11198 #, 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:11383 +#: access/transam/xlog.c:11385 #, c-format msgid "exclusive backup not in progress" msgstr "ексклюзивне резервне копіювання не виконується" -#: access/transam/xlog.c:11410 +#: access/transam/xlog.c:11412 #, c-format msgid "a backup is not in progress" msgstr "резервне копіювання не виконується" -#: 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/xlog.c:11498 access/transam/xlog.c:11511 +#: access/transam/xlog.c:11902 access/transam/xlog.c:11908 +#: access/transam/xlog.c:11956 access/transam/xlog.c:12029 #: access/transam/xlogfuncs.c:692 #, c-format msgid "invalid data in file \"%s\"" msgstr "невірні дані у файлі \"%s\"" -#: access/transam/xlog.c:11513 replication/basebackup.c:1277 +#: access/transam/xlog.c:11515 replication/basebackup.c:1277 #, c-format msgid "the standby was promoted during online backup" msgstr "режим очікування було підвищено у процесі резервного копіювання \"на ходу\"" -#: access/transam/xlog.c:11514 replication/basebackup.c:1278 +#: access/transam/xlog.c:11516 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:11561 +#: access/transam/xlog.c:11563 #, c-format msgid "WAL generated with full_page_writes=off was replayed during online backup" msgstr "У процесі резервного копіювання \"на ходу\" був відтворений WAL, створений в режимі full_page_writes=off" -#: access/transam/xlog.c:11681 +#: access/transam/xlog.c:11683 #, c-format msgid "base backup done, waiting for required WAL segments to be archived" msgstr "резервне копіювання виконане, очікуються необхідні сегменти WAL для архівації" -#: access/transam/xlog.c:11693 +#: access/transam/xlog.c:11695 #, c-format msgid "still waiting for all required WAL segments to be archived (%d seconds elapsed)" msgstr "все ще чекає на необхідні сегменти WAL для архівації (%d секунд пройшло)" -#: access/transam/xlog.c:11695 +#: access/transam/xlog.c:11697 #, 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:11702 +#: access/transam/xlog.c:11704 #, c-format msgid "all required WAL segments have been archived" msgstr "усі необхідні сегменти WAL архівовані" -#: access/transam/xlog.c:11706 +#: access/transam/xlog.c:11708 #, 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:11761 +#: access/transam/xlog.c:11763 #, c-format msgid "aborting backup due to backend exiting before pg_stop_backup was called" msgstr "припинення резервного копіювання через завершення обслуговуючого процесу до виклику pg_stop_backup" -#: access/transam/xlog.c:11937 +#: access/transam/xlog.c:11939 #, c-format msgid "backup time %s in file \"%s\"" msgstr "час резервного копіювання %s у файлі \"%s\"" -#: access/transam/xlog.c:11942 +#: access/transam/xlog.c:11944 #, c-format msgid "backup label %s in file \"%s\"" msgstr "мітка резервного копіювання %s у файлі \"%s\"" -#: access/transam/xlog.c:11955 +#: access/transam/xlog.c:11957 #, c-format msgid "Timeline ID parsed is %u, but expected %u." msgstr "Проаналізовано ID часової лінії %u, очіувалося %u." -#: access/transam/xlog.c:11959 +#: access/transam/xlog.c:11961 #, c-format msgid "backup timeline %u in file \"%s\"" msgstr "лінія часу резервного копіювання %u у файлі \"%s\"" #. translator: %s is a WAL record description -#: access/transam/xlog.c:12067 +#: access/transam/xlog.c:12069 #, c-format msgid "WAL redo at %X/%X for %s" msgstr "запис REDO в WAL в позиції %X/%X для %s" -#: access/transam/xlog.c:12116 +#: access/transam/xlog.c:12118 #, c-format msgid "online backup mode was not canceled" msgstr "режим копіювання онлайн не був відмінений" -#: access/transam/xlog.c:12117 +#: access/transam/xlog.c:12119 #, c-format msgid "File \"%s\" could not be renamed to \"%s\": %m." msgstr "Файл \"%s\" не може бути перейменований на \"%s\": %m." -#: access/transam/xlog.c:12126 access/transam/xlog.c:12138 -#: access/transam/xlog.c:12148 +#: access/transam/xlog.c:12128 access/transam/xlog.c:12140 +#: access/transam/xlog.c:12150 #, c-format msgid "online backup mode canceled" msgstr "режим копіювання онлайн був відмінений" -#: access/transam/xlog.c:12139 +#: access/transam/xlog.c:12141 #, c-format msgid "Files \"%s\" and \"%s\" were renamed to \"%s\" and \"%s\", respectively." msgstr "Файли \"%s\" і \"%s\" було перейменовано на \"%s\" і \"%s\" відповідно." -#: access/transam/xlog.c:12149 +#: access/transam/xlog.c:12151 #, 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:12282 access/transam/xlogutils.c:971 +#: access/transam/xlog.c:12284 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:12288 access/transam/xlogutils.c:978 +#: access/transam/xlog.c:12290 access/transam/xlogutils.c:978 #, c-format msgid "could not read from log segment %s, offset %u: read %d of %zu" msgstr "не вдалося прочитати сегмент журналу %s, зсув %u: прочитано %d з %zu" -#: access/transam/xlog.c:12831 +#: access/transam/xlog.c:12847 #, c-format msgid "WAL receiver process shutdown requested" msgstr "Запит на вимкнення процесу приймача WAL" -#: access/transam/xlog.c:12937 +#: access/transam/xlog.c:12953 #, c-format msgid "received promote request" msgstr "отримано запит підвищення статусу" -#: access/transam/xlog.c:12950 +#: access/transam/xlog.c:12966 #, c-format msgid "promote trigger file found: %s" msgstr "знайдено файл тригера підвищення: %s" -#: access/transam/xlog.c:12959 +#: access/transam/xlog.c:12975 #, c-format msgid "could not stat promote trigger file \"%s\": %m" msgstr "не вдалося отримати інформацію про файл тригера підвищення \"%s\": %m" @@ -3033,7 +3039,7 @@ #: utils/adt/jsonfuncs.c:1904 utils/adt/jsonfuncs.c:2092 #: utils/adt/jsonfuncs.c:2201 utils/adt/jsonfuncs.c:3663 utils/adt/misc.c:216 #: utils/adt/pgstatfuncs.c:476 utils/adt/pgstatfuncs.c:584 -#: utils/adt/pgstatfuncs.c:1719 utils/fmgr/funcapi.c:72 utils/misc/guc.c:9698 +#: utils/adt/pgstatfuncs.c:1719 utils/fmgr/funcapi.c:72 utils/misc/guc.c:9705 #: utils/mmgr/portalmem.c:1145 #, c-format msgid "set-valued function called in context that cannot accept a set" @@ -3048,7 +3054,7 @@ #: storage/ipc/shmem.c:554 utils/adt/datetime.c:4769 utils/adt/genfile.c:509 #: utils/adt/genfile.c:592 utils/adt/misc.c:220 utils/adt/pgstatfuncs.c:480 #: utils/adt/pgstatfuncs.c:588 utils/adt/pgstatfuncs.c:1723 -#: utils/misc/guc.c:9702 utils/misc/pg_config.c:43 utils/mmgr/portalmem.c:1149 +#: utils/misc/guc.c:9709 utils/misc/pg_config.c:43 utils/mmgr/portalmem.c:1149 #, c-format msgid "materialize mode required, but it is not allowed in this context" msgstr "необхідний режим матеріалізації (materialize mode), але він неприпустимий у цьому контексті" @@ -3105,7 +3111,7 @@ msgid "\"wait_seconds\" must not be negative or zero" msgstr "\"wait_seconds\" не має бути від'ємним чи нулем" -#: access/transam/xlogfuncs.c:748 storage/ipc/signalfuncs.c:164 +#: access/transam/xlogfuncs.c:748 storage/ipc/signalfuncs.c:169 #, c-format msgid "failed to send signal to postmaster: %m" msgstr "надіслати сигнал процесу postmaster не вдалося: %m" @@ -3115,137 +3121,132 @@ msgid "server did not promote within %d seconds" msgstr "сервер не підвищено протягом %d секунд" -#: access/transam/xlogreader.c:354 +#: access/transam/xlogreader.c:323 #, c-format msgid "invalid record offset at %X/%X" msgstr "невірний зсув запису: %X/%X" -#: access/transam/xlogreader.c:362 +#: access/transam/xlogreader.c:331 #, c-format msgid "contrecord is requested by %X/%X" msgstr "по зсуву %X/%X запитано продовження запису" -#: access/transam/xlogreader.c:403 access/transam/xlogreader.c:733 +#: access/transam/xlogreader.c:372 access/transam/xlogreader.c:719 #, c-format msgid "invalid record length at %X/%X: wanted %u, got %u" msgstr "невірна довжина запису по зсуву %X/%X: очікувалось %u, отримано %u" -#: access/transam/xlogreader.c:429 -#, c-format -msgid "record length %u at %X/%X too long" -msgstr "довжина запису %u на %X/%X є задовгою" - -#: access/transam/xlogreader.c:478 +#: access/transam/xlogreader.c:442 #, c-format msgid "there is no contrecord flag at %X/%X" msgstr "немає прапора contrecord на %X/%X" -#: access/transam/xlogreader.c:491 +#: access/transam/xlogreader.c:455 #, c-format msgid "invalid contrecord length %u at %X/%X" msgstr "невірна довжина contrecord %u на %X/%X" -#: access/transam/xlogreader.c:741 +#: access/transam/xlogreader.c:727 #, c-format msgid "invalid resource manager ID %u at %X/%X" msgstr "невірний ID менеджера ресурсів %u в %X/%X" -#: access/transam/xlogreader.c:755 access/transam/xlogreader.c:772 +#: access/transam/xlogreader.c:741 access/transam/xlogreader.c:758 #, c-format msgid "record with incorrect prev-link %X/%X at %X/%X" msgstr "запис з неправильним попереднім посиланням %X/%X на %X/%X" -#: access/transam/xlogreader.c:809 +#: access/transam/xlogreader.c:797 #, c-format msgid "incorrect resource manager data checksum in record at %X/%X" msgstr "некоректна контрольна сума даних менеджера ресурсів у запису по зсуву %X/%X" -#: access/transam/xlogreader.c:846 +#: access/transam/xlogreader.c:834 #, c-format msgid "invalid magic number %04X in log segment %s, offset %u" msgstr "невірне магічне число %04X в сегменті журналу %s, зсув %u" -#: access/transam/xlogreader.c:860 access/transam/xlogreader.c:901 +#: access/transam/xlogreader.c:848 access/transam/xlogreader.c:889 #, c-format msgid "invalid info bits %04X in log segment %s, offset %u" msgstr "невірні інформаційні біти %04X в сегменті журналу %s, зсув %u" -#: access/transam/xlogreader.c:875 +#: access/transam/xlogreader.c:863 #, c-format msgid "WAL file is from different database system: WAL file database system identifier is %llu, pg_control database system identifier is %llu" msgstr "WAL файл належить іншій системі баз даних: ідентифікатор системи баз даних де міститься WAL файл - %llu, а ідентифікатор системи баз даних pg_control - %llu" -#: access/transam/xlogreader.c:883 +#: access/transam/xlogreader.c:871 #, c-format msgid "WAL file is from different database system: incorrect segment size in page header" msgstr "Файл WAL належить іншій системі баз даних: некоректний розмір сегменту в заголовку сторінки" -#: access/transam/xlogreader.c:889 +#: access/transam/xlogreader.c:877 #, c-format msgid "WAL file is from different database system: incorrect XLOG_BLCKSZ in page header" msgstr "Файл WAL належить іншій системі баз даних: некоректний XLOG_BLCKSZ в заголовку сторінки" -#: access/transam/xlogreader.c:920 +#: access/transam/xlogreader.c:908 #, c-format msgid "unexpected pageaddr %X/%X in log segment %s, offset %u" msgstr "неочікуваний pageaddr %X/%X в сегменті журналу %s, зсув %u" -#: access/transam/xlogreader.c:945 +#: access/transam/xlogreader.c:933 #, c-format msgid "out-of-sequence timeline ID %u (after %u) in log segment %s, offset %u" msgstr "порушення послідовності ID лінії часу %u (після %u) в сегменті журналу %s, зсув %u" -#: access/transam/xlogreader.c:1285 +#: access/transam/xlogreader.c:1273 #, c-format msgid "out-of-order block_id %u at %X/%X" msgstr "ідентифікатор блока %u out-of-order в позиції %X/%X" -#: access/transam/xlogreader.c:1308 +#: access/transam/xlogreader.c:1296 #, c-format msgid "BKPBLOCK_HAS_DATA set, but no data included at %X/%X" msgstr "BKPBLOCK_HAS_DATA встановлений, але немає даних в позиції %X/%X" -#: access/transam/xlogreader.c:1315 +#: access/transam/xlogreader.c:1303 #, c-format msgid "BKPBLOCK_HAS_DATA not set, but data length is %u at %X/%X" msgstr "BKPBLOCK_HAS_DATA встановлений, але довжина даних дорівнює %u в позиції %X/%X" -#: access/transam/xlogreader.c:1351 +#: access/transam/xlogreader.c:1339 #, c-format msgid "BKPIMAGE_HAS_HOLE set, but hole offset %u length %u block image length %u at %X/%X" msgstr "BKPIMAGE_HAS_HOLE встановлений, але для пропуску задані: зсув %u, довжина %u, при довжині образу блока %u в позиції %X/%X" -#: access/transam/xlogreader.c:1367 +#: access/transam/xlogreader.c:1355 #, c-format msgid "BKPIMAGE_HAS_HOLE not set, but hole offset %u length %u at %X/%X" msgstr "BKPIMAGE_HAS_HOLE не встановлений, але для пропуску задані: зсув %u, довжина %u в позиції %X/%X" -#: access/transam/xlogreader.c:1382 +#: access/transam/xlogreader.c:1370 #, c-format msgid "BKPIMAGE_IS_COMPRESSED set, but block image length %u at %X/%X" msgstr "BKPIMAGE_IS_COMPRESSED встановлений, але довжина образу блока дорівнює %u в позиції %X/%X" -#: access/transam/xlogreader.c:1397 +#: access/transam/xlogreader.c:1385 #, c-format msgid "neither BKPIMAGE_HAS_HOLE nor BKPIMAGE_IS_COMPRESSED set, but block image length is %u at %X/%X" msgstr "ні BKPIMAGE_HAS_HOLE, ні BKPIMAGE_IS_COMPRESSED не встановлені, але довжина образу блока дорвінює %u в позиції %X/%X" -#: access/transam/xlogreader.c:1413 +#: access/transam/xlogreader.c:1401 #, c-format msgid "BKPBLOCK_SAME_REL set but no previous rel at %X/%X" msgstr "BKPBLOCK_SAME_REL встановлений, але попереднє значення не задано в позиції %X/%X" -#: access/transam/xlogreader.c:1425 +#: access/transam/xlogreader.c:1413 #, c-format msgid "invalid block_id %u at %X/%X" msgstr "невірний ідентифікатор блоку %u в позиції %X/%X" -#: access/transam/xlogreader.c:1514 +#: access/transam/xlogreader.c:1502 #, c-format msgid "record with invalid length at %X/%X" msgstr "запис з невірною довжиною на %X/%X" -#: access/transam/xlogreader.c:1603 +#: access/transam/xlogreader.c:1591 #, c-format msgid "invalid compressed image at %X/%X, block %d" msgstr "невірно стиснутий образ в позиції %X/%X, блок %d" @@ -3458,7 +3459,7 @@ msgstr "речення IN SCHEMA не можна використати в GRANT/REVOKE ON SCHEMAS" #: 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/analyze.c:389 commands/copy.c:5095 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 @@ -3468,7 +3469,7 @@ #: 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/analyze.c:2368 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 @@ -3477,7 +3478,7 @@ msgstr "стовпець \"%s\" зв'язку \"%s\" не існує" #: catalog/aclchk.c:1824 catalog/objectaddress.c:1267 commands/sequence.c:1148 -#: commands/tablecmds.c:236 commands/tablecmds.c:16115 utils/adt/acl.c:2059 +#: commands/tablecmds.c:236 commands/tablecmds.c:16123 utils/adt/acl.c:2059 #: utils/adt/acl.c:2089 utils/adt/acl.c:2121 utils/adt/acl.c:2153 #: utils/adt/acl.c:2181 utils/adt/acl.c:2211 #, c-format @@ -3912,8 +3913,8 @@ msgid "foreign server with OID %u does not exist" msgstr "стороннього серверу з OID %u не усніє" -#: catalog/aclchk.c:4423 catalog/aclchk.c:4762 utils/cache/typcache.c:378 -#: utils/cache/typcache.c:432 +#: catalog/aclchk.c:4423 catalog/aclchk.c:4762 utils/cache/typcache.c:383 +#: utils/cache/typcache.c:437 #, c-format msgid "type with OID %u does not exist" msgstr "тип з OID %u не існує" @@ -4057,10 +4058,10 @@ #: 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 +#: storage/lmgr/deadlock.c:1153 storage/lmgr/proc.c:1364 utils/misc/guc.c:6783 +#: utils/misc/guc.c:6819 utils/misc/guc.c:6889 utils/misc/guc.c:11012 +#: utils/misc/guc.c:11046 utils/misc/guc.c:11080 utils/misc/guc.c:11123 +#: utils/misc/guc.c:11165 #, c-format msgid "%s" msgstr "%s" @@ -4170,100 +4171,100 @@ msgid "cannot add NO INHERIT constraint to partitioned table \"%s\"" msgstr "не можна додати обмеження NO INHERIT до секціонованої таблиці \"%s\"" -#: catalog/heap.c:2685 +#: catalog/heap.c:2686 #, c-format msgid "check constraint \"%s\" already exists" msgstr "обмеження перевірки \"%s\" вже інсує" -#: catalog/heap.c:2855 catalog/index.c:881 catalog/pg_constraint.c:668 +#: catalog/heap.c:2856 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\" вже існує" -#: catalog/heap.c:2862 +#: catalog/heap.c:2863 #, c-format msgid "constraint \"%s\" conflicts with non-inherited constraint on relation \"%s\"" msgstr "обмеження \"%s\" конфліктує з неуспадкованим обмеженням відношення \"%s\"" -#: catalog/heap.c:2873 +#: catalog/heap.c:2874 #, c-format msgid "constraint \"%s\" conflicts with inherited constraint on relation \"%s\"" msgstr "обмеження \"%s\" конфліктує з успадкованим обмеженням відношення \"%s\"" -#: catalog/heap.c:2883 +#: catalog/heap.c:2884 #, c-format msgid "constraint \"%s\" conflicts with NOT VALID constraint on relation \"%s\"" msgstr "обмеження \"%s\" конфліктує з обмеженням NOT VALID в відношенні \"%s\"" -#: catalog/heap.c:2888 +#: catalog/heap.c:2889 #, c-format msgid "merging constraint \"%s\" with inherited definition" msgstr "злиття обмеження \"%s\" з успадкованим визначенням" -#: catalog/heap.c:2993 +#: catalog/heap.c:2994 #, c-format msgid "cannot use generated column \"%s\" in column generation expression" msgstr "в виразі створення стовпця не можна використовувати згенерований стовпець \"%s\" " -#: catalog/heap.c:2995 +#: catalog/heap.c:2996 #, c-format msgid "A generated column cannot reference another generated column." msgstr "Згенерований стовпець не може посилатися на інший згенерований стовпець." -#: catalog/heap.c:3001 +#: catalog/heap.c:3002 #, c-format msgid "cannot use whole-row variable in column generation expression" msgstr "у виразі створення стовпців не можна використовувати змінну усього рядка" -#: catalog/heap.c:3002 +#: catalog/heap.c:3003 #, c-format msgid "This would cause the generated column to depend on its own value." msgstr "Це призведе до того, що згенерований стовпець буде залежати від власного значення." -#: catalog/heap.c:3055 +#: catalog/heap.c:3058 #, c-format msgid "generation expression is not immutable" msgstr "вираз генерації не є незмінним" -#: catalog/heap.c:3083 rewrite/rewriteHandler.c:1238 +#: catalog/heap.c:3086 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 +#: catalog/heap.c:3091 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 "Потрібно буде переписати або привести вираз." -#: catalog/heap.c:3135 +#: catalog/heap.c:3138 #, c-format msgid "only table \"%s\" can be referenced in check constraint" msgstr "в обмеженні-перевірці можна посилатися лише на таблицю \"%s\"" -#: catalog/heap.c:3433 +#: catalog/heap.c:3436 #, c-format msgid "unsupported ON COMMIT and foreign key combination" msgstr "непідтримуване поєднання зовнішнього ключа з ON COMMIT" -#: catalog/heap.c:3434 +#: catalog/heap.c:3437 #, c-format msgid "Table \"%s\" references \"%s\", but they do not have the same ON COMMIT setting." msgstr "Таблиця \"%s\" посилається на \"%s\", але вони не мають той же параметр ON COMMIT." -#: catalog/heap.c:3439 +#: catalog/heap.c:3442 #, c-format msgid "cannot truncate a table referenced in a foreign key constraint" msgstr "скоротити таблицю, на яку посилається зовнішній ключ, не можливо" -#: catalog/heap.c:3440 +#: catalog/heap.c:3443 #, c-format msgid "Table \"%s\" references \"%s\"." msgstr "Таблиця \"%s\" посилається на \"%s\"." -#: catalog/heap.c:3442 +#: catalog/heap.c:3445 #, c-format msgid "Truncate table \"%s\" at the same time, or use TRUNCATE ... CASCADE." msgstr "Скоротіть таблицю \"%s\" паралельно або використайте TRUNCATE ... CASCADE." @@ -4324,12 +4325,12 @@ msgid "DROP INDEX CONCURRENTLY must be first action in transaction" msgstr "DROP INDEX CONCURRENTLY повинен бути першою дією в транзакції" -#: catalog/index.c:2958 +#: catalog/index.c:2967 #, c-format msgid "building index \"%s\" on table \"%s\" serially" msgstr "створення індексу \"%s\" в таблиці \"%s\" у непаралельному режимі (serially)" -#: catalog/index.c:2963 +#: catalog/index.c:2972 #, 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" @@ -4338,27 +4339,27 @@ msgstr[2] "створення індексу \"%s\" в таблиці \"%s\" з розрахунком на %d паралельних виконавців" msgstr[3] "створення індексу \"%s\" в таблиці \"%s\" з розрахунком на %d паралельних виконавців" -#: catalog/index.c:3597 +#: catalog/index.c:3606 #, c-format msgid "cannot reindex temporary tables of other sessions" msgstr "повторно індексувати тимчасові таблиці інших сеансів не можна" -#: catalog/index.c:3608 commands/indexcmds.c:3151 +#: catalog/index.c:3617 commands/indexcmds.c:3127 #, c-format msgid "cannot reindex invalid index on TOAST table" msgstr "переіндексувати неприпустимий індекс в таблиці TOAST не можна" -#: catalog/index.c:3730 +#: catalog/index.c:3739 #, c-format msgid "index \"%s\" was reindexed" msgstr "індекс \"%s\" був перебудований" -#: catalog/index.c:3812 commands/indexcmds.c:3172 +#: catalog/index.c:3821 commands/indexcmds.c:3148 #, c-format msgid "REINDEX of partitioned tables is not yet implemented, skipping \"%s\"" msgstr "REINDEX для секціонованих таблиць ще не реалізовано, пропускається \"%s\"" -#: catalog/index.c:3867 +#: catalog/index.c:3876 #, c-format msgid "cannot reindex invalid index \"%s.%s\" on TOAST table, skipping" msgstr "переіндексувати неприпустимий індекс \"%s.%s\" в таблиці TOAST не можна, пропускається" @@ -4500,7 +4501,7 @@ msgstr "не можна створити тимчасові таблиці під час паралельної операції" #: catalog/namespace.c:4293 commands/tablespace.c:1216 commands/variable.c:64 -#: utils/misc/guc.c:11189 utils/misc/guc.c:11267 +#: utils/misc/guc.c:11197 utils/misc/guc.c:11275 #, c-format msgid "List syntax is invalid." msgstr "Помилка синтаксису у списку." @@ -4514,19 +4515,19 @@ msgstr "\"%s\" не є таблицею" #: catalog/objectaddress.c:1282 commands/tablecmds.c:242 -#: commands/tablecmds.c:5787 commands/tablecmds.c:16120 commands/view.c:119 +#: commands/tablecmds.c:5787 commands/tablecmds.c:16128 commands/view.c:119 #, c-format msgid "\"%s\" is not a view" msgstr "\"%s\" не є поданням" #: catalog/objectaddress.c:1289 commands/matview.c:186 commands/tablecmds.c:248 -#: commands/tablecmds.c:16125 +#: commands/tablecmds.c:16133 #, c-format msgid "\"%s\" is not a materialized view" msgstr "\"%s\" не є матеріалізованим поданням" #: catalog/objectaddress.c:1296 commands/tablecmds.c:266 -#: commands/tablecmds.c:5790 commands/tablecmds.c:16130 +#: commands/tablecmds.c:5790 commands/tablecmds.c:16138 #, c-format msgid "\"%s\" is not a foreign table" msgstr "\"%s\" не є сторонньою таблицею" @@ -5527,7 +5528,7 @@ msgstr "неприпустима сторінка в блоці %u відношення %s" #: catalog/toasting.c:112 commands/indexcmds.c:664 commands/tablecmds.c:5760 -#: commands/tablecmds.c:15985 +#: commands/tablecmds.c:15993 #, c-format msgid "\"%s\" is not a table or materialized view" msgstr "\"%s\" не є таблицею або матеріалізованим поданням" @@ -5957,7 +5958,7 @@ msgid "must be superuser to import system collations" msgstr "імпортувати систмені правила сортування може тільки суперкористувач" -#: commands/collationcmds.c:575 commands/copy.c:1897 commands/copy.c:3484 +#: commands/collationcmds.c:575 commands/copy.c:1897 commands/copy.c:3488 #: libpq/be-secure-common.c:81 #, c-format msgid "could not execute command \"%s\": %m" @@ -6320,7 +6321,7 @@ msgid "COPY TO instructs the PostgreSQL server process to write a file. You may want a client-side facility such as psql's \\copy." msgstr "COPY TO наказує серверному процесу PostgreSQL записати дані до файлу. Можливо, вам потрібна клієнтська команда, наприклад \\copy в psql." -#: commands/copy.c:1947 commands/copy.c:3515 +#: commands/copy.c:1947 commands/copy.c:3519 #, c-format msgid "\"%s\" is a directory" msgstr "\"%s\" - каталог" @@ -6390,142 +6391,142 @@ msgid "cannot perform COPY FREEZE because the table was not created or truncated in the current subtransaction" msgstr "не можна виконати COPY FREEZE, тому, що таблиця не була створена або скорочена в поточній підтранзакції" -#: commands/copy.c:3502 +#: commands/copy.c:3506 #, c-format msgid "COPY FROM instructs the PostgreSQL server process to read a file. You may want a client-side facility such as psql's \\copy." msgstr "COPY FROM наказує серверному процесу PostgreSQL прочитати дані з файлу. Можливо, вам потрібна клієнтська команда, наприклад \\copy в psql." -#: commands/copy.c:3530 +#: commands/copy.c:3534 #, c-format msgid "COPY file signature not recognized" msgstr "Підпис COPY-файлу не розпізнано" -#: commands/copy.c:3535 +#: commands/copy.c:3539 #, c-format msgid "invalid COPY file header (missing flags)" msgstr "невірний заголовок файлу COPY (відсутні прапори)" -#: commands/copy.c:3539 +#: commands/copy.c:3543 #, c-format msgid "invalid COPY file header (WITH OIDS)" msgstr "невірний заголовок файла COPY (WITH OIDS)" -#: commands/copy.c:3544 +#: commands/copy.c:3548 #, c-format msgid "unrecognized critical flags in COPY file header" msgstr "не розпізнано важливі прапори в заголовку файлу COPY" -#: commands/copy.c:3550 +#: commands/copy.c:3554 #, c-format msgid "invalid COPY file header (missing length)" msgstr "невірний заголовок файлу COPY (відсутня довжина)" -#: commands/copy.c:3557 +#: commands/copy.c:3561 #, c-format msgid "invalid COPY file header (wrong length)" msgstr "невірний заголовок файлу COPY (невірна довжина)" -#: commands/copy.c:3675 commands/copy.c:4348 commands/copy.c:4578 +#: commands/copy.c:3679 commands/copy.c:4352 commands/copy.c:4582 #, c-format msgid "extra data after last expected column" msgstr "зайві дані після вмісту останнього стовпця" -#: commands/copy.c:3689 +#: commands/copy.c:3693 #, c-format msgid "missing data for column \"%s\"" msgstr "відсутні дані для стовпця \"%s\"" -#: commands/copy.c:3772 +#: commands/copy.c:3776 #, c-format msgid "received copy data after EOF marker" msgstr "після маркера кінця файлу продовжуються дані COPY" -#: commands/copy.c:3779 +#: commands/copy.c:3783 #, c-format msgid "row field count is %d, expected %d" msgstr "кількість полів у рядку: %d, очікувалось: %d" -#: commands/copy.c:4099 commands/copy.c:4116 +#: commands/copy.c:4103 commands/copy.c:4120 #, c-format msgid "literal carriage return found in data" msgstr "в даних виявлено явне повернення каретки" -#: commands/copy.c:4100 commands/copy.c:4117 +#: commands/copy.c:4104 commands/copy.c:4121 #, c-format msgid "unquoted carriage return found in data" msgstr "в даних виявлено повернення каретки без лапок" -#: commands/copy.c:4102 commands/copy.c:4119 +#: commands/copy.c:4106 commands/copy.c:4123 #, c-format msgid "Use \"\\r\" to represent carriage return." msgstr "Використайте \"\\r\", щоб позначити повернення каретки." -#: commands/copy.c:4103 commands/copy.c:4120 +#: commands/copy.c:4107 commands/copy.c:4124 #, c-format msgid "Use quoted CSV field to represent carriage return." msgstr "Використайте CSV в лапках, щоб позначити повернення каретки." -#: commands/copy.c:4132 +#: commands/copy.c:4136 #, c-format msgid "literal newline found in data" msgstr "в даних знайдено явний новий рядок" -#: commands/copy.c:4133 +#: commands/copy.c:4137 #, c-format msgid "unquoted newline found in data" msgstr "в даних знайдено новий рядок без лапок" -#: commands/copy.c:4135 +#: commands/copy.c:4139 #, c-format msgid "Use \"\\n\" to represent newline." msgstr "Використайте \"\\n\", щоб представити новий рядок." -#: commands/copy.c:4136 +#: commands/copy.c:4140 #, c-format msgid "Use quoted CSV field to represent newline." msgstr "Використайте CSV в лапках, щоб позначити новий рядок." -#: commands/copy.c:4182 commands/copy.c:4218 +#: commands/copy.c:4186 commands/copy.c:4222 #, c-format msgid "end-of-copy marker does not match previous newline style" msgstr "маркер \"кінець копії\" не відповідає попередньому стилю нового рядка" -#: commands/copy.c:4191 commands/copy.c:4207 +#: commands/copy.c:4195 commands/copy.c:4211 #, c-format msgid "end-of-copy marker corrupt" msgstr "маркер \"кінець копії\" зіпсований" -#: commands/copy.c:4662 +#: commands/copy.c:4666 #, c-format msgid "unterminated CSV quoted field" msgstr "незакінчене поле в лапках CSV" -#: commands/copy.c:4739 commands/copy.c:4758 +#: commands/copy.c:4743 commands/copy.c:4762 #, c-format msgid "unexpected EOF in COPY data" msgstr "неочікуваний кінец файлу в даних COPY" -#: commands/copy.c:4748 +#: commands/copy.c:4752 #, c-format msgid "invalid field size" msgstr "невірний розмір поля" -#: commands/copy.c:4771 +#: commands/copy.c:4775 #, c-format msgid "incorrect binary data format" msgstr "невірний двійковий формат даних" -#: commands/copy.c:5079 +#: commands/copy.c:5083 #, c-format msgid "column \"%s\" is a generated column" msgstr "стовпець \"%s\" є згенерованим стовпцем" -#: commands/copy.c:5081 +#: commands/copy.c:5085 #, c-format msgid "Generated columns cannot be used in COPY." msgstr "Згенеровані стовпці не можна використовувати в COPY." -#: commands/copy.c:5096 commands/indexcmds.c:1806 commands/statscmds.c:228 +#: commands/copy.c:5100 commands/indexcmds.c:1782 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 @@ -6533,7 +6534,7 @@ msgid "column \"%s\" does not exist" msgstr "стовпця \"%s\" не існує" -#: commands/copy.c:5103 commands/tablecmds.c:2231 commands/trigger.c:893 +#: commands/copy.c:5107 commands/tablecmds.c:2231 commands/trigger.c:893 #: parser/parse_target.c:1051 parser/parse_target.c:1062 #, c-format msgid "column \"%s\" specified more than once" @@ -6805,7 +6806,7 @@ msgstr[2] "Є %d інших сеансів з використанням цієї бази даних." msgstr[3] "Є %d інших сеансів з використанням цієї бази даних." -#: commands/dbcommands.c:2129 storage/ipc/procarray.c:3129 +#: commands/dbcommands.c:2129 storage/ipc/procarray.c:3128 #, c-format msgid "There is %d prepared transaction using the database." msgid_plural "There are %d prepared transactions using the database." @@ -7881,198 +7882,198 @@ msgid "%s constraints cannot be used when partition keys include expressions." msgstr "обмеження %s не можуть використовуватись, якщо ключі секціонування включають вирази." -#: commands/indexcmds.c:1018 +#: commands/indexcmds.c:1021 #, c-format msgid "unique constraint on partitioned table must include all partitioning columns" msgstr "обмеження унікальності в секціонованій таблиці повинно включати всі стовпці секціонування" -#: commands/indexcmds.c:1019 +#: commands/indexcmds.c:1022 #, c-format msgid "%s constraint on table \"%s\" lacks column \"%s\" which is part of the partition key." msgstr "в обмеженні %s таблиці\"%s\" не вистачає стовпця \"%s\", що є частиною ключа секціонування." -#: commands/indexcmds.c:1038 commands/indexcmds.c:1057 +#: commands/indexcmds.c:1041 commands/indexcmds.c:1060 #, c-format msgid "index creation on system columns is not supported" msgstr "створення індексу для системних стовпців не підтримується" -#: commands/indexcmds.c:1082 +#: commands/indexcmds.c:1085 #, c-format msgid "%s %s will create implicit index \"%s\" for table \"%s\"" msgstr "%s %s створить неявний індекс \"%s\" для таблиці \"%s\"" -#: commands/indexcmds.c:1253 tcop/utility.c:1510 +#: commands/indexcmds.c:1256 tcop/utility.c:1510 #, c-format msgid "cannot create unique index on partitioned table \"%s\"" msgstr "не можна створити унікальний індекс в секціонованій таблиці \"%s\"" -#: commands/indexcmds.c:1255 tcop/utility.c:1512 +#: commands/indexcmds.c:1258 tcop/utility.c:1512 #, c-format msgid "Table \"%s\" contains partitions that are foreign tables." msgstr "Таблиця \"%s\" містить секції, які є зовнішніми таблицями." -#: commands/indexcmds.c:1723 +#: commands/indexcmds.c:1699 #, c-format msgid "functions in index predicate must be marked IMMUTABLE" msgstr "функції в предикаті індексу повинні бути позначені як IMMUTABLE" -#: commands/indexcmds.c:1801 parser/parse_utilcmd.c:2485 +#: commands/indexcmds.c:1777 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:1825 parser/parse_utilcmd.c:1821 +#: commands/indexcmds.c:1801 parser/parse_utilcmd.c:1821 #, c-format msgid "expressions are not supported in included columns" msgstr "вирази не підтримуються у включених стовпцях " -#: commands/indexcmds.c:1866 +#: commands/indexcmds.c:1842 #, c-format msgid "functions in index expression must be marked IMMUTABLE" msgstr "функції в індексному виразі повинні бути позначені як IMMUTABLE" -#: commands/indexcmds.c:1881 +#: commands/indexcmds.c:1857 #, c-format msgid "including column does not support a collation" msgstr "включені стовпці не підтримують правила сортування" -#: commands/indexcmds.c:1885 +#: commands/indexcmds.c:1861 #, c-format msgid "including column does not support an operator class" msgstr "включені стовпці не підтримують класи операторів" -#: commands/indexcmds.c:1889 +#: commands/indexcmds.c:1865 #, c-format msgid "including column does not support ASC/DESC options" msgstr "включені стовпці не підтримують параметри ASC/DESC" -#: commands/indexcmds.c:1893 +#: commands/indexcmds.c:1869 #, c-format msgid "including column does not support NULLS FIRST/LAST options" msgstr "включені стовпці не підтримують параметри NULLS FIRST/LAST" -#: commands/indexcmds.c:1934 +#: commands/indexcmds.c:1910 #, c-format msgid "could not determine which collation to use for index expression" msgstr "не вдалося визначити, яке правило сортування використати для індексного виразу" -#: commands/indexcmds.c:1942 commands/tablecmds.c:16451 commands/typecmds.c:771 +#: commands/indexcmds.c:1918 commands/tablecmds.c:16461 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:2007 +#: commands/indexcmds.c:1983 #, c-format msgid "operator %s is not commutative" msgstr "оператор %s не комутативний" -#: commands/indexcmds.c:2009 +#: commands/indexcmds.c:1985 #, c-format msgid "Only commutative operators can be used in exclusion constraints." msgstr "В обмеженнях-виключеннях можуть використовуватись лише комутативні оператори." -#: commands/indexcmds.c:2035 +#: commands/indexcmds.c:2011 #, c-format msgid "operator %s is not a member of operator family \"%s\"" msgstr "оператор %s не є членом сімейства операторів \"%s\"" -#: commands/indexcmds.c:2038 +#: commands/indexcmds.c:2014 #, c-format msgid "The exclusion operator must be related to the index operator class for the constraint." msgstr "Оператор винятку для обмеження повинен відноситись до класу операторів індексу." -#: commands/indexcmds.c:2073 +#: commands/indexcmds.c:2049 #, c-format msgid "access method \"%s\" does not support ASC/DESC options" msgstr "метод доступу \"%s\" не підтримує параметри ASC/DESC" -#: commands/indexcmds.c:2078 +#: commands/indexcmds.c:2054 #, c-format msgid "access method \"%s\" does not support NULLS FIRST/LAST options" msgstr "метод доступу \"%s\" не підтримує параметри NULLS FIRST/LAST" -#: commands/indexcmds.c:2124 commands/tablecmds.c:16476 -#: commands/tablecmds.c:16482 commands/typecmds.c:1947 +#: commands/indexcmds.c:2100 commands/tablecmds.c:16486 +#: commands/tablecmds.c:16492 commands/typecmds.c:1947 #, c-format msgid "data type %s has no default operator class for access method \"%s\"" msgstr "тип даних %s не має класу операторів за замовчуванням для методу доступу \"%s\"" -#: commands/indexcmds.c:2126 +#: commands/indexcmds.c:2102 #, 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:2155 commands/indexcmds.c:2163 +#: commands/indexcmds.c:2131 commands/indexcmds.c:2139 #: commands/opclasscmds.c:208 #, c-format msgid "operator class \"%s\" does not exist for access method \"%s\"" msgstr "клас операторів \"%s\" не існує для методу доступу \"%s\"" -#: commands/indexcmds.c:2177 commands/typecmds.c:1935 +#: commands/indexcmds.c:2153 commands/typecmds.c:1935 #, c-format msgid "operator class \"%s\" does not accept data type %s" msgstr "клас операторів \"%s\" не приймає тип даних %s" -#: commands/indexcmds.c:2267 +#: commands/indexcmds.c:2243 #, c-format msgid "there are multiple default operator classes for data type %s" msgstr "для типу даних %s є кілька класів операторів за замовчуванням" -#: commands/indexcmds.c:2716 +#: commands/indexcmds.c:2692 #, c-format msgid "table \"%s\" has no indexes that can be reindexed concurrently" msgstr "таблиця \"%s\" не має індексів, які можна переіндексувати паралельно" -#: commands/indexcmds.c:2727 +#: commands/indexcmds.c:2703 #, c-format msgid "table \"%s\" has no indexes to reindex" msgstr "таблиця \"%s\" не має індексів для переіндексування" -#: commands/indexcmds.c:2766 commands/indexcmds.c:3047 -#: commands/indexcmds.c:3140 +#: commands/indexcmds.c:2742 commands/indexcmds.c:3023 +#: commands/indexcmds.c:3116 #, c-format msgid "cannot reindex system catalogs concurrently" msgstr "не можна конкурентно переіндексувати системні каталоги" -#: commands/indexcmds.c:2789 +#: commands/indexcmds.c:2765 #, c-format msgid "can only reindex the currently open database" msgstr "переіндексувати можна тільки наразі відкриту базу даних" -#: commands/indexcmds.c:2880 +#: commands/indexcmds.c:2856 #, c-format msgid "cannot reindex system catalogs concurrently, skipping all" msgstr "не можна конкурентно переіндексувати системні каталоги, пропускаємо" -#: commands/indexcmds.c:2932 commands/indexcmds.c:3672 +#: commands/indexcmds.c:2908 commands/indexcmds.c:3648 #, c-format msgid "table \"%s.%s\" was reindexed" msgstr "таблиця \"%s.%s\" була переіндексована" -#: commands/indexcmds.c:3062 commands/indexcmds.c:3108 +#: commands/indexcmds.c:3038 commands/indexcmds.c:3084 #, c-format msgid "cannot reindex invalid index \"%s.%s\" concurrently, skipping" msgstr "неможливо переіндексувати пошкоджений індекс \"%s.%s\" паралельно, пропускається" -#: commands/indexcmds.c:3068 +#: commands/indexcmds.c:3044 #, c-format msgid "cannot reindex exclusion constraint index \"%s.%s\" concurrently, skipping" msgstr "неможливо переіндексувати індекс обмеження-виключення \"%s.%s\" паралельно, пропускається" -#: commands/indexcmds.c:3179 +#: commands/indexcmds.c:3155 #, c-format msgid "cannot reindex this type of relation concurrently" msgstr "неможливо переіндексувати цей тип відношень паралельон" -#: commands/indexcmds.c:3654 commands/indexcmds.c:3665 +#: commands/indexcmds.c:3630 commands/indexcmds.c:3641 #, c-format msgid "index \"%s.%s\" was reindexed" msgstr "індекс \"%s.%s\" був перебудований" -#: commands/indexcmds.c:3697 +#: commands/indexcmds.c:3673 #, c-format msgid "REINDEX is not yet implemented for partitioned indexes" msgstr "REINDEX для секціонованих індексів ще не реалізований" @@ -8378,8 +8379,8 @@ #: commands/policy.c:89 commands/policy.c:382 commands/statscmds.c:143 #: commands/tablecmds.c:1540 commands/tablecmds.c:2023 #: commands/tablecmds.c:3105 commands/tablecmds.c:5730 -#: commands/tablecmds.c:8596 commands/tablecmds.c:16041 -#: commands/tablecmds.c:16076 commands/trigger.c:309 commands/trigger.c:1214 +#: commands/tablecmds.c:8596 commands/tablecmds.c:16049 +#: commands/tablecmds.c:16084 commands/trigger.c:309 commands/trigger.c:1214 #: commands/trigger.c:1323 rewrite/rewriteDefine.c:278 #: rewrite/rewriteDefine.c:956 rewrite/rewriteRemove.c:80 #, c-format @@ -8798,7 +8799,7 @@ msgstr "для створення підписок потрібно бути суперкористувачем" #: commands/subscriptioncmds.c:445 commands/subscriptioncmds.c:534 -#: replication/logical/tablesync.c:861 replication/logical/worker.c:2167 +#: replication/logical/tablesync.c:871 replication/logical/worker.c:2167 #, c-format msgid "could not connect to the publisher: %s" msgstr "не вдалося підключитись до сервера публікації: %s" @@ -8860,7 +8861,7 @@ msgstr "не вдалося з'єднатися з сервером публікації для видалення слота реплікації \"%s\"" #: commands/subscriptioncmds.c:993 commands/subscriptioncmds.c:1009 -#: replication/logical/tablesync.c:910 replication/logical/tablesync.c:932 +#: replication/logical/tablesync.c:920 replication/logical/tablesync.c:942 #, c-format msgid "The error was: %s" msgstr "Сталася помилка: %s" @@ -8952,7 +8953,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:17689 +#: commands/tablecmds.c:252 commands/tablecmds.c:276 commands/tablecmds.c:17699 #: parser/parse_utilcmd.c:2217 #, c-format msgid "index \"%s\" does not exist" @@ -9913,7 +9914,7 @@ msgid "cannot change owner of sequence \"%s\"" msgstr "неможливо змінити власника послідовності \"%s\"" -#: commands/tablecmds.c:12914 commands/tablecmds.c:16152 +#: commands/tablecmds.c:12914 commands/tablecmds.c:16160 #, c-format msgid "Use ALTER TYPE instead." msgstr "Замість цього використайте ALTER TYPE." @@ -9993,12 +9994,12 @@ msgid "cannot inherit from a partition" msgstr "успадкування від секції неможливе" -#: commands/tablecmds.c:14031 commands/tablecmds.c:16792 +#: commands/tablecmds.c:14031 commands/tablecmds.c:16802 #, c-format msgid "circular inheritance not allowed" msgstr "циклічне успадкування неприпустиме" -#: commands/tablecmds.c:14032 commands/tablecmds.c:16793 +#: commands/tablecmds.c:14032 commands/tablecmds.c:16803 #, c-format msgid "\"%s\" is already a child of \"%s\"." msgstr "\"%s\" вже є нащадком \"%s\"." @@ -10158,186 +10159,186 @@ msgid "relation \"%s\" already exists in schema \"%s\"" msgstr "відношення \"%s\" вже існує в схемі \"%s\"" -#: commands/tablecmds.c:16135 +#: commands/tablecmds.c:16143 #, c-format msgid "\"%s\" is not a composite type" msgstr "\"%s\" - не складений тип" -#: commands/tablecmds.c:16167 +#: commands/tablecmds.c:16175 #, c-format msgid "\"%s\" is not a table, view, materialized view, sequence, or foreign table" msgstr "\"%s\" - не таблиця, подання, матеріалізоване подання, послідовність або зовнішня таблиця" -#: commands/tablecmds.c:16202 +#: commands/tablecmds.c:16210 #, c-format msgid "unrecognized partitioning strategy \"%s\"" msgstr "нерозпізнана стратегія секціонування \"%s\"" -#: commands/tablecmds.c:16210 +#: commands/tablecmds.c:16218 #, c-format msgid "cannot use \"list\" partition strategy with more than one column" msgstr "стратегія секціонування \"по списку\" не може використовувати декілька стовпців" -#: commands/tablecmds.c:16276 +#: commands/tablecmds.c:16284 #, c-format msgid "column \"%s\" named in partition key does not exist" msgstr "стовпець \"%s\", згаданий в ключі секціонування, не існує" -#: commands/tablecmds.c:16284 +#: commands/tablecmds.c:16292 #, c-format msgid "cannot use system column \"%s\" in partition key" msgstr "системний стовпець \"%s\" не можна використати в ключі секціонування" -#: commands/tablecmds.c:16295 commands/tablecmds.c:16409 +#: commands/tablecmds.c:16303 commands/tablecmds.c:16393 #, c-format msgid "cannot use generated column in partition key" msgstr "використати згенерований стовпець в ключі секції, не можна" -#: commands/tablecmds.c:16296 commands/tablecmds.c:16410 commands/trigger.c:649 +#: commands/tablecmds.c:16304 commands/tablecmds.c:16394 commands/trigger.c:649 #: rewrite/rewriteHandler.c:875 rewrite/rewriteHandler.c:892 #, c-format msgid "Column \"%s\" is a generated column." msgstr "Стовпець \"%s\" є згенерованим стовпцем." -#: commands/tablecmds.c:16372 -#, c-format -msgid "functions in partition key expression must be marked IMMUTABLE" -msgstr "функції у виразі ключа секціонування повинні бути позначені як IMMUTABLE" - -#: commands/tablecmds.c:16392 +#: commands/tablecmds.c:16376 #, c-format msgid "partition key expressions cannot contain system column references" msgstr "вирази ключа секціонування не можуть містити посилання на системний стовпець" -#: commands/tablecmds.c:16422 +#: commands/tablecmds.c:16423 +#, c-format +msgid "functions in partition key expression must be marked IMMUTABLE" +msgstr "функції у виразі ключа секціонування повинні бути позначені як IMMUTABLE" + +#: commands/tablecmds.c:16432 #, c-format msgid "cannot use constant expression as partition key" msgstr "не можна використати константий вираз як ключ секціонування" -#: commands/tablecmds.c:16443 +#: commands/tablecmds.c:16453 #, c-format msgid "could not determine which collation to use for partition expression" msgstr "не вдалося визначити, яке правило сортування використати для виразу секціонування" -#: commands/tablecmds.c:16478 +#: commands/tablecmds.c:16488 #, c-format msgid "You must specify a hash operator class or define a default hash operator class for the data type." msgstr "Ви повинні вказати клас операторів гешування або визначити клас операторів гешування за замовчуванням для цього типу даних." -#: commands/tablecmds.c:16484 +#: commands/tablecmds.c:16494 #, c-format msgid "You must specify a btree operator class or define a default btree operator class for the data type." msgstr "Ви повинні вказати клас операторів (btree) або визначити клас операторів (btree) за замовчуванням для цього типу даних." -#: commands/tablecmds.c:16629 +#: commands/tablecmds.c:16639 #, c-format msgid "partition constraint for table \"%s\" is implied by existing constraints" msgstr "обмеження секції для таблиці \"%s\" має на увазі наявні обмеження" -#: commands/tablecmds.c:16633 partitioning/partbounds.c:3119 +#: commands/tablecmds.c:16643 partitioning/partbounds.c:3119 #: partitioning/partbounds.c:3170 #, c-format msgid "updated partition constraint for default partition \"%s\" is implied by existing constraints" msgstr "оновлене обмеження секції для секції за замовчуванням \"%s\" має на увазі наявні обмеження" -#: commands/tablecmds.c:16732 +#: commands/tablecmds.c:16742 #, c-format msgid "\"%s\" is already a partition" msgstr "\"%s\" вже є секцією" -#: commands/tablecmds.c:16738 +#: commands/tablecmds.c:16748 #, c-format msgid "cannot attach a typed table as partition" msgstr "неможливо підключити типізовану таблицю в якості секції" -#: commands/tablecmds.c:16754 +#: commands/tablecmds.c:16764 #, c-format msgid "cannot attach inheritance child as partition" msgstr "неможливо підключити нащадка успадкування в якості секції" -#: commands/tablecmds.c:16768 +#: commands/tablecmds.c:16778 #, c-format msgid "cannot attach inheritance parent as partition" msgstr "неможливо підключити предка успадкування в якості секції" -#: commands/tablecmds.c:16802 +#: commands/tablecmds.c:16812 #, c-format msgid "cannot attach a temporary relation as partition of permanent relation \"%s\"" msgstr "неможливо підкючити тимчасове відношення в якості секції постійного відношення \"%s\"" -#: commands/tablecmds.c:16810 +#: commands/tablecmds.c:16820 #, c-format msgid "cannot attach a permanent relation as partition of temporary relation \"%s\"" msgstr "неможливо підключити постійне відношення в якості секції тимчасового відношення \"%s\"" -#: commands/tablecmds.c:16818 +#: commands/tablecmds.c:16828 #, c-format msgid "cannot attach as partition of temporary relation of another session" msgstr "неможливо підключити секцію до тимчасового відношення в іншому сеансі" -#: commands/tablecmds.c:16825 +#: commands/tablecmds.c:16835 #, c-format msgid "cannot attach temporary relation of another session as partition" msgstr "неможливо підключити тимчасове відношення з іншого сеансу в якості секції" -#: commands/tablecmds.c:16845 +#: commands/tablecmds.c:16855 #, c-format msgid "table \"%s\" contains column \"%s\" not found in parent \"%s\"" msgstr "таблиця \"%s\" містить стовпець \"%s\", відсутній в батьківській \"%s\"" -#: commands/tablecmds.c:16848 +#: commands/tablecmds.c:16858 #, c-format msgid "The new partition may contain only the columns present in parent." msgstr "Нова секція може містити лише стовпці, що є у батьківській таблиці." -#: commands/tablecmds.c:16860 +#: commands/tablecmds.c:16870 #, c-format msgid "trigger \"%s\" prevents table \"%s\" from becoming a partition" msgstr "тригер \"%s\" не дозволяє зробити таблицю \"%s\" секцією" -#: commands/tablecmds.c:16862 commands/trigger.c:455 +#: commands/tablecmds.c:16872 commands/trigger.c:455 #, c-format msgid "ROW triggers with transition tables are not supported on partitions" msgstr "Тригери ROW з перехідними таблицями для секцій не підтримуються" -#: commands/tablecmds.c:17041 +#: commands/tablecmds.c:17051 #, c-format msgid "cannot attach foreign table \"%s\" as partition of partitioned table \"%s\"" msgstr "не можна підключити зовнішню таблицю \"%s\" в якості секції секціонованої таблиці \"%s\"" -#: commands/tablecmds.c:17044 +#: commands/tablecmds.c:17054 #, c-format msgid "Table \"%s\" contains unique indexes." msgstr "Таблиця \"%s\" містить унікальні індекси." -#: commands/tablecmds.c:17723 commands/tablecmds.c:17743 -#: commands/tablecmds.c:17763 commands/tablecmds.c:17782 -#: commands/tablecmds.c:17824 +#: commands/tablecmds.c:17733 commands/tablecmds.c:17753 +#: commands/tablecmds.c:17773 commands/tablecmds.c:17792 +#: commands/tablecmds.c:17834 #, c-format msgid "cannot attach index \"%s\" as a partition of index \"%s\"" msgstr "неможливо підключити індекс \"%s\" в якості секції індексу \"%s\"" -#: commands/tablecmds.c:17726 +#: commands/tablecmds.c:17736 #, c-format msgid "Index \"%s\" is already attached to another index." msgstr "Індекс \"%s\" вже підключений до іншого індексу." -#: commands/tablecmds.c:17746 +#: commands/tablecmds.c:17756 #, c-format msgid "Index \"%s\" is not an index on any partition of table \"%s\"." msgstr "Індекс \"%s\" не є індексом жодної секції таблиці \"%s\"." -#: commands/tablecmds.c:17766 +#: commands/tablecmds.c:17776 #, c-format msgid "The index definitions do not match." msgstr "Визначення індексів не співпадають." -#: commands/tablecmds.c:17785 +#: commands/tablecmds.c:17795 #, 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:17827 +#: commands/tablecmds.c:17837 #, c-format msgid "Another index is already attached for partition \"%s\"." msgstr "До секції \"%s\" вже підключений інший індекс." @@ -11449,7 +11450,7 @@ msgid "skipping \"%s\" --- cannot vacuum non-tables or special system tables" msgstr "пропускається \"%s\" --- очищати не таблиці або спеціальні системні таблиці не можна" -#: commands/variable.c:165 utils/misc/guc.c:11229 utils/misc/guc.c:11291 +#: commands/variable.c:165 utils/misc/guc.c:11237 utils/misc/guc.c:11299 #, c-format msgid "Unrecognized key word: \"%s\"." msgstr "Нерозпізнане ключове слово: \"%s\"." @@ -11645,7 +11646,7 @@ msgid "no value found for parameter %d" msgstr "не знайдено значення для параметру %d" -#: executor/execExpr.c:893 parser/parse_agg.c:808 +#: executor/execExpr.c:893 parser/parse_agg.c:819 #, c-format msgid "window function calls cannot be nested" msgstr "виклики віконних функцій не можуть бути вкладеними" @@ -11671,10 +11672,10 @@ msgstr[3] "функції не можна передати більше ніж %d аргументів" #: 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 +#: executor/execExprInterp.c:2760 utils/adt/arrayfuncs.c:263 +#: utils/adt/arrayfuncs.c:563 utils/adt/arrayfuncs.c:1305 +#: utils/adt/arrayfuncs.c:3395 utils/adt/arrayfuncs.c:5357 +#: utils/adt/arrayfuncs.c:5874 #, c-format msgid "number of array dimensions (%d) exceeds the maximum allowed (%d)" msgstr "число вимірів масива (%d) перевищує ліміт (%d)" @@ -11698,7 +11699,7 @@ #: 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 +#: utils/fmgr/funcapi.c:490 #, c-format msgid "type %s is not composite" msgstr "тип %s не є складеним" @@ -11724,11 +11725,14 @@ msgstr "для багатовимірних масивів повинні задаватись вирази з відповідними вимірами" #: 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 +#: utils/adt/arrayfuncs.c:936 utils/adt/arrayfuncs.c:1523 +#: utils/adt/arrayfuncs.c:2330 utils/adt/arrayfuncs.c:2345 +#: utils/adt/arrayfuncs.c:2604 utils/adt/arrayfuncs.c:2620 +#: utils/adt/arrayfuncs.c:2927 utils/adt/arrayfuncs.c:2942 +#: utils/adt/arrayfuncs.c:3283 utils/adt/arrayfuncs.c:3425 +#: utils/adt/arrayfuncs.c:5966 utils/adt/arrayfuncs.c:6307 +#: utils/adt/arrayutils.c:88 utils/adt/arrayutils.c:97 +#: utils/adt/arrayutils.c:104 #, c-format msgid "array size exceeds the maximum allowed (%d)" msgstr "розмір масиву перевищує максимальний допустимий розмір (%d)" @@ -12005,8 +12009,8 @@ #: 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 +#: utils/adt/arrayfuncs.c:3675 utils/adt/arrayfuncs.c:4195 +#: utils/adt/arrayfuncs.c:6187 utils/adt/rowtypes.c:1182 #, c-format msgid "could not identify an equality operator for type %s" msgstr "не вдалося визначити оператора рівності для типу %s" @@ -12185,7 +12189,7 @@ msgid "unexpected EOF for tape %d: requested %zu bytes, read %zu bytes" msgstr "неочікуваний обрив для стрічки %d: запитано %zu байт, прочитано %zu байт" -#: executor/nodeAgg.c:4048 parser/parse_agg.c:650 parser/parse_agg.c:678 +#: executor/nodeAgg.c:4048 parser/parse_agg.c:661 parser/parse_agg.c:689 #, c-format msgid "aggregate function calls cannot be nested" msgstr "виклики агрегатних функцій не можуть бути вкладеними" @@ -12392,7 +12396,7 @@ msgid "DECLARE SCROLL CURSOR ... FOR UPDATE/SHARE is not supported" msgstr "DECLARE SCROLL CURSOR ... FOR UPDATE/SHARE не підтримується" -#: executor/spi.c:1548 parser/analyze.c:2468 +#: executor/spi.c:1548 parser/analyze.c:2505 #, c-format msgid "Scrollable cursors must be READ ONLY." msgstr "Курсори з прокручуванням повинні бути READ ONLY." @@ -12422,7 +12426,7 @@ msgid "Valid options in this context are: %s" msgstr "У цьому контексті припустимі параметри: %s" -#: jit/llvm/llvmjit.c:732 +#: jit/llvm/llvmjit.c:882 #, c-format msgid "time to inline: %.3fs, opt: %.3fs, emit: %.3fs" msgstr "час впровадження: %.3fs, оптимізації: %.3fs, видачі: %.3fs" @@ -13238,16 +13242,16 @@ msgid "File must have permissions u=rw (0600) or less if owned by the database user, or permissions u=rw,g=r (0640) or less if owned by root." msgstr "Файл повинен мати дозволи u=rw (0600) або менше, якщо він належить користувачу бази даних, або u=rw,g=r (0640) або менше, якщо він належить кореню." -#: libpq/be-secure-gssapi.c:204 +#: libpq/be-secure-gssapi.c:201 msgid "GSSAPI wrap error" msgstr "помилка при згортанні GSSAPI" -#: libpq/be-secure-gssapi.c:211 +#: libpq/be-secure-gssapi.c:208 #, c-format msgid "outgoing GSSAPI message would not use confidentiality" msgstr "вихідне повідомлення GSSAPI не буде використовувати конфіденційність" -#: libpq/be-secure-gssapi.c:218 libpq/be-secure-gssapi.c:622 +#: libpq/be-secure-gssapi.c:215 libpq/be-secure-gssapi.c:622 #, c-format msgid "server tried to send oversize GSSAPI packet (%zu > %zu)" msgstr "сервер намагався надіслати переповнений пакет GSSAPI (%zu > %zu)" @@ -13360,92 +13364,92 @@ msgid "could not set SSL socket: %s" msgstr "не вдалося встановити SSL-сокет: %s" -#: libpq/be-secure-openssl.c:466 +#: libpq/be-secure-openssl.c:467 #, c-format msgid "could not accept SSL connection: %m" msgstr "не вдалося прийняти SSL-підключення: %m" -#: libpq/be-secure-openssl.c:470 libpq/be-secure-openssl.c:523 +#: libpq/be-secure-openssl.c:471 libpq/be-secure-openssl.c:524 #, c-format msgid "could not accept SSL connection: EOF detected" msgstr "не вдалося прийняти SSL-підключення: виявлений EOF" -#: libpq/be-secure-openssl.c:509 +#: libpq/be-secure-openssl.c:510 #, c-format msgid "could not accept SSL connection: %s" msgstr "не вдалося отримати підключення SSL: %s" -#: libpq/be-secure-openssl.c:512 +#: libpq/be-secure-openssl.c:513 #, c-format msgid "This may indicate that the client does not support any SSL protocol version between %s and %s." msgstr "Це може вказувати, що клієнт не підтримує жодної версії протоколу SSL між %s і %s." -#: libpq/be-secure-openssl.c:528 libpq/be-secure-openssl.c:659 -#: libpq/be-secure-openssl.c:723 +#: libpq/be-secure-openssl.c:529 libpq/be-secure-openssl.c:660 +#: libpq/be-secure-openssl.c:730 #, c-format msgid "unrecognized SSL error code: %d" msgstr "нерозпізнаний код помилки SSL: %d" -#: libpq/be-secure-openssl.c:570 +#: libpq/be-secure-openssl.c:571 #, c-format msgid "SSL certificate's common name contains embedded null" msgstr "Спільне ім'я SSL-сертифікату містить нульовий байт" -#: libpq/be-secure-openssl.c:648 libpq/be-secure-openssl.c:707 +#: libpq/be-secure-openssl.c:649 libpq/be-secure-openssl.c:714 #, c-format msgid "SSL error: %s" msgstr "Помилка SSL: %s" -#: libpq/be-secure-openssl.c:889 +#: libpq/be-secure-openssl.c:891 #, c-format msgid "could not open DH parameters file \"%s\": %m" msgstr "не вдалося відкрити файл параметрів DH \"%s\": %m" -#: libpq/be-secure-openssl.c:901 +#: libpq/be-secure-openssl.c:903 #, c-format msgid "could not load DH parameters file: %s" msgstr "не вдалося завантажити файл параметрів DH: %s" -#: libpq/be-secure-openssl.c:911 +#: libpq/be-secure-openssl.c:913 #, c-format msgid "invalid DH parameters: %s" msgstr "неприпустимі параметри DH: %s" -#: libpq/be-secure-openssl.c:920 +#: libpq/be-secure-openssl.c:922 #, c-format msgid "invalid DH parameters: p is not prime" msgstr "неприпустимі параметри DH: р - не штрих" -#: libpq/be-secure-openssl.c:929 +#: libpq/be-secure-openssl.c:931 #, c-format msgid "invalid DH parameters: neither suitable generator or safe prime" msgstr "неприпустимі параметри DH: немає придатного генератора або безпечного штриха" -#: libpq/be-secure-openssl.c:1086 +#: libpq/be-secure-openssl.c:1088 #, c-format msgid "DH: could not load DH parameters" msgstr "DH: не вдалося завантажити параметри DH" -#: libpq/be-secure-openssl.c:1094 +#: libpq/be-secure-openssl.c:1096 #, c-format msgid "DH: could not set DH parameters: %s" msgstr "DH: не вдалося встановити параметри DH: %s" -#: libpq/be-secure-openssl.c:1121 +#: libpq/be-secure-openssl.c:1123 #, c-format msgid "ECDH: unrecognized curve name: %s" msgstr "ECDH: нерозпізнане ім'я кривої: %s" -#: libpq/be-secure-openssl.c:1130 +#: libpq/be-secure-openssl.c:1132 #, c-format msgid "ECDH: could not create key" msgstr "ECDH: не вдалося створити ключ" -#: libpq/be-secure-openssl.c:1158 +#: libpq/be-secure-openssl.c:1160 msgid "no SSL error reported" msgstr "немає повідомлення про помилку SSL" -#: libpq/be-secure-openssl.c:1162 +#: libpq/be-secure-openssl.c:1164 #, c-format msgid "SSL error code %lu" msgstr "Код помилки SSL %lu" @@ -13973,32 +13977,32 @@ msgid "there is no client connection" msgstr "немає клієнтського підключення" -#: libpq/pqcomm.c:962 libpq/pqcomm.c:1058 +#: libpq/pqcomm.c:967 libpq/pqcomm.c:1068 #, c-format msgid "could not receive data from client: %m" msgstr "не вдалось отримати дані від клієнта: %m" -#: libpq/pqcomm.c:1215 tcop/postgres.c:4187 +#: libpq/pqcomm.c:1225 tcop/postgres.c:4187 #, c-format msgid "terminating connection because protocol synchronization was lost" msgstr "завершення підключення через втрату синхронізації протоколу" -#: libpq/pqcomm.c:1281 +#: libpq/pqcomm.c:1291 #, c-format msgid "unexpected EOF within message length word" msgstr "неочікуваний EOF в слові довжини повідомлення" -#: libpq/pqcomm.c:1292 +#: libpq/pqcomm.c:1302 #, c-format msgid "invalid message length" msgstr "неприпустима довжина повідомлення" -#: libpq/pqcomm.c:1314 libpq/pqcomm.c:1327 +#: libpq/pqcomm.c:1324 libpq/pqcomm.c:1337 #, c-format msgid "incomplete message from client" msgstr "неповне повідомлення від клієнта" -#: libpq/pqcomm.c:1460 +#: libpq/pqcomm.c:1470 #, c-format msgid "could not send data to client: %m" msgstr "не вдалось надіслати дані клієнту: %m" @@ -14009,7 +14013,7 @@ msgstr "у повідомлення не залишилось даних" #: libpq/pqformat.c:517 libpq/pqformat.c:535 libpq/pqformat.c:556 -#: utils/adt/arrayfuncs.c:1460 utils/adt/rowtypes.c:567 +#: utils/adt/arrayfuncs.c:1461 utils/adt/rowtypes.c:567 #, c-format msgid "insufficient data left in message" msgstr "недостатьно даних залишилось в повідомленні" @@ -14300,7 +14304,7 @@ #: nodes/nodeFuncs.c:122 nodes/nodeFuncs.c:153 parser/parse_coerce.c:2295 #: parser/parse_coerce.c:2404 parser/parse_coerce.c:2439 #: parser/parse_expr.c:2212 parser/parse_func.c:701 parser/parse_oper.c:967 -#: utils/fmgr/funcapi.c:528 +#: utils/fmgr/funcapi.c:562 #, c-format msgid "could not find array type for data type %s" msgstr "не вдалося знайти тип масиву для типу даних %s" @@ -14327,8 +14331,8 @@ msgstr "%s не можна застосовувати до нульової сторони зовнішнього з’єднання" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: optimizer/plan/planner.c:1923 parser/analyze.c:1632 parser/analyze.c:1848 -#: parser/analyze.c:2675 +#: optimizer/plan/planner.c:1923 parser/analyze.c:1669 parser/analyze.c:1885 +#: parser/analyze.c:2712 #, c-format msgid "%s is not allowed with UNION/INTERSECT/EXCEPT" msgstr "%s несумісно з UNION/INTERSECT/EXCEPT" @@ -14390,7 +14394,7 @@ msgid "could not implement %s" msgstr "не вдалося реалізувати %s" -#: optimizer/util/clauses.c:4772 +#: optimizer/util/clauses.c:4838 #, c-format msgid "SQL function \"%s\" during inlining" msgstr "Впроваджена в код SQL-функція \"%s\"" @@ -14425,509 +14429,509 @@ msgid "there is no unique or exclusion constraint matching the ON CONFLICT specification" msgstr "немає унікального обмеження або обмеження-виключення відповідного специфікації ON CONFLICT" -#: parser/analyze.c:705 parser/analyze.c:1401 +#: parser/analyze.c:742 parser/analyze.c:1438 #, c-format msgid "VALUES lists must all be the same length" msgstr "Списки VALUES повинні мати однакову довжину" -#: parser/analyze.c:904 +#: parser/analyze.c:941 #, c-format msgid "INSERT has more expressions than target columns" msgstr "INSERT містить більше виразів, ніж цільових стовпців" -#: parser/analyze.c:922 +#: parser/analyze.c:959 #, c-format msgid "INSERT has more target columns than expressions" msgstr "INSERT містить більше цільових стовпців, ніж виразів" -#: parser/analyze.c:926 +#: parser/analyze.c:963 #, c-format msgid "The insertion source is a row expression containing the same number of columns expected by the INSERT. Did you accidentally use extra parentheses?" msgstr "Джерелом даних є вираз рядка, який містить стільки ж стовпців, скільки потребується для INSERT. Ви випадково використовували додаткові дужки?" -#: parser/analyze.c:1210 parser/analyze.c:1605 +#: parser/analyze.c:1247 parser/analyze.c:1642 #, c-format msgid "SELECT ... INTO is not allowed here" msgstr "SELECT ... INTO не дозволяється тут" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:1535 parser/analyze.c:2878 +#: parser/analyze.c:1572 parser/analyze.c:2915 #, c-format msgid "%s cannot be applied to VALUES" msgstr "%s не можна застосовувати до VALUES" -#: parser/analyze.c:1770 +#: parser/analyze.c:1807 #, c-format msgid "invalid UNION/INTERSECT/EXCEPT ORDER BY clause" msgstr "неприпустиме речення UNION/INTERSECT/EXCEPT ORDER BY" -#: parser/analyze.c:1771 +#: parser/analyze.c:1808 #, c-format msgid "Only result column names can be used, not expressions or functions." msgstr "Дозволено використання тільки імен стовпців, але не виразів або функцій." -#: parser/analyze.c:1772 +#: parser/analyze.c:1809 #, c-format msgid "Add the expression/function to every SELECT, or move the UNION into a FROM clause." msgstr "Додайте вираз/функція до кожного SELECT, або перемістіть UNION у речення FROM." -#: parser/analyze.c:1838 +#: parser/analyze.c:1875 #, c-format msgid "INTO is only allowed on first SELECT of UNION/INTERSECT/EXCEPT" msgstr "INTO дозволяється додати лише до першого SELECT в UNION/INTERSECT/EXCEPT" -#: parser/analyze.c:1910 +#: parser/analyze.c:1947 #, c-format msgid "UNION/INTERSECT/EXCEPT member statement cannot refer to other relations of same query level" msgstr "Учасник інструкції UNION/INTERSECT/EXCEPT не може посилатись на інші відносини на тому ж рівні" -#: parser/analyze.c:1997 +#: parser/analyze.c:2034 #, c-format msgid "each %s query must have the same number of columns" msgstr "кожен %s запит повинен мати однакову кількість стовпців" -#: parser/analyze.c:2386 +#: parser/analyze.c:2423 #, c-format msgid "RETURNING must have at least one column" msgstr "В RETURNING повинен бути мінімум один стовпець" -#: parser/analyze.c:2427 +#: parser/analyze.c:2464 #, c-format msgid "cannot specify both SCROLL and NO SCROLL" msgstr "не можна вказати SCROLL і NO SCROLL одночасно" -#: parser/analyze.c:2446 +#: parser/analyze.c:2483 #, c-format msgid "DECLARE CURSOR must not contain data-modifying statements in WITH" msgstr "DECLARE CURSOR не повинен містити операторів, які змінюють дані в WITH" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2454 +#: parser/analyze.c:2491 #, c-format msgid "DECLARE CURSOR WITH HOLD ... %s is not supported" msgstr "DECLARE CURSOR WITH HOLD ... %s не підтримується" -#: parser/analyze.c:2457 +#: parser/analyze.c:2494 #, c-format msgid "Holdable cursors must be READ ONLY." msgstr "Курсори, що зберігаються повинні бути READ ONLY." #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2465 +#: parser/analyze.c:2502 #, c-format msgid "DECLARE SCROLL CURSOR ... %s is not supported" msgstr "DECLARE SCROLL CURSOR ... %s не підтримується" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2476 +#: parser/analyze.c:2513 #, c-format msgid "DECLARE INSENSITIVE CURSOR ... %s is not supported" msgstr "DECLARE INSENSITIVE CURSOR ... %s не підтримується" -#: parser/analyze.c:2479 +#: parser/analyze.c:2516 #, c-format msgid "Insensitive cursors must be READ ONLY." msgstr "Нечутливі курсори повинні бути READ ONLY." -#: parser/analyze.c:2545 +#: parser/analyze.c:2582 #, c-format msgid "materialized views must not use data-modifying statements in WITH" msgstr "в матеріалізованих поданнях не повинні використовуватись оператори, які змінюють дані в WITH" -#: parser/analyze.c:2555 +#: parser/analyze.c:2592 #, c-format msgid "materialized views must not use temporary tables or views" msgstr "в матеріалізованих поданнях не повинні використовуватись тимчасові таблиці або подання" -#: parser/analyze.c:2565 +#: parser/analyze.c:2602 #, c-format msgid "materialized views may not be defined using bound parameters" msgstr "визначати матеріалізовані подання з зв'язаними параметрами не можна" -#: parser/analyze.c:2577 +#: parser/analyze.c:2614 #, c-format msgid "materialized views cannot be unlogged" msgstr "матеріалізовані подання не можуть бути нежурнальованими" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2682 +#: parser/analyze.c:2719 #, c-format msgid "%s is not allowed with DISTINCT clause" msgstr "%s не дозволяється з реченням DISTINCT" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2689 +#: parser/analyze.c:2726 #, c-format msgid "%s is not allowed with GROUP BY clause" msgstr "%s не дозволяється з реченням GROUP BY" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2696 +#: parser/analyze.c:2733 #, c-format msgid "%s is not allowed with HAVING clause" msgstr "%s не дозволяється з реченням HAVING" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2703 +#: parser/analyze.c:2740 #, c-format msgid "%s is not allowed with aggregate functions" msgstr "%s не дозволяється з агрегатними функціями" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2710 +#: parser/analyze.c:2747 #, c-format msgid "%s is not allowed with window functions" msgstr "%s не дозволяється з віконними функціями" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2717 +#: parser/analyze.c:2754 #, c-format msgid "%s is not allowed with set-returning functions in the target list" msgstr "%s не дозволяється з функціями, які повертають безлічі, в цільовому списку" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2809 +#: parser/analyze.c:2846 #, c-format msgid "%s must specify unqualified relation names" msgstr "для %s потрібно вказати некваліфіковані імена відносин" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2851 +#: parser/analyze.c:2888 #, c-format msgid "%s cannot be applied to a join" msgstr "%s не можна застосовувати до з'єднання" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2860 +#: parser/analyze.c:2897 #, c-format msgid "%s cannot be applied to a function" msgstr "%s не можна застосовувати до функції" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2869 +#: parser/analyze.c:2906 #, c-format msgid "%s cannot be applied to a table function" msgstr "%s не можна застосовувати до табличної функції" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2887 +#: parser/analyze.c:2924 #, c-format msgid "%s cannot be applied to a WITH query" msgstr "%s не можна застосовувати до запиту WITH" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2896 +#: parser/analyze.c:2933 #, c-format msgid "%s cannot be applied to a named tuplestore" msgstr "%s не можна застосовувати до іменованого джерела кортежів" #. translator: %s is a SQL row locking clause such as FOR UPDATE -#: parser/analyze.c:2916 +#: parser/analyze.c:2953 #, c-format msgid "relation \"%s\" in %s clause not found in FROM clause" msgstr "відношення \"%s\" в реченні %s не знайдено в реченні FROM" -#: parser/parse_agg.c:220 parser/parse_oper.c:222 +#: parser/parse_agg.c:208 parser/parse_oper.c:222 #, c-format msgid "could not identify an ordering operator for type %s" msgstr "для типу %s не вдалося визначити оператора сортування" -#: parser/parse_agg.c:222 +#: parser/parse_agg.c:210 #, c-format msgid "Aggregates with DISTINCT must be able to sort their inputs." msgstr "Агрегатним функціям з DISTINCT необхідно сортувати їх вхідні дані." -#: parser/parse_agg.c:257 +#: parser/parse_agg.c:268 #, c-format msgid "GROUPING must have fewer than 32 arguments" msgstr "GROUPING повинно містити меньше, ніж 32 аргумента" -#: parser/parse_agg.c:360 +#: parser/parse_agg.c:371 msgid "aggregate functions are not allowed in JOIN conditions" msgstr "агрегатні функції не дозволяються в умовах JOIN" -#: parser/parse_agg.c:362 +#: parser/parse_agg.c:373 msgid "grouping operations are not allowed in JOIN conditions" msgstr "операції групування не дозволяються в умовах JOIN" -#: parser/parse_agg.c:374 +#: parser/parse_agg.c:385 msgid "aggregate functions are not allowed in FROM clause of their own query level" msgstr "агрегатні функції не можна застосовувати в реченні FROM їх рівня запиту" -#: parser/parse_agg.c:376 +#: parser/parse_agg.c:387 msgid "grouping operations are not allowed in FROM clause of their own query level" msgstr "операції групування не можна застосовувати в реченні FROM їх рівня запиту" -#: parser/parse_agg.c:381 +#: parser/parse_agg.c:392 msgid "aggregate functions are not allowed in functions in FROM" msgstr "агрегатні функції не можна застосовувати у функціях у FROM" -#: parser/parse_agg.c:383 +#: parser/parse_agg.c:394 msgid "grouping operations are not allowed in functions in FROM" msgstr "операції групування не можна застосовувати у функціях у FROM" -#: parser/parse_agg.c:391 +#: parser/parse_agg.c:402 msgid "aggregate functions are not allowed in policy expressions" msgstr "агрегатні функції не можна застосовувати у виразах політики" -#: parser/parse_agg.c:393 +#: parser/parse_agg.c:404 msgid "grouping operations are not allowed in policy expressions" msgstr "операції групування не можна застосовувати у виразах політики" -#: parser/parse_agg.c:410 +#: parser/parse_agg.c:421 msgid "aggregate functions are not allowed in window RANGE" msgstr "агрегатні функції не можна застосовувати у вікні RANGE " -#: parser/parse_agg.c:412 +#: parser/parse_agg.c:423 msgid "grouping operations are not allowed in window RANGE" msgstr "операції групування не можна застосовувати у вікні RANGE" -#: parser/parse_agg.c:417 +#: parser/parse_agg.c:428 msgid "aggregate functions are not allowed in window ROWS" msgstr "агрегатні функції не можна застосовувати у вікні ROWS" -#: parser/parse_agg.c:419 +#: parser/parse_agg.c:430 msgid "grouping operations are not allowed in window ROWS" msgstr "операції групування не можна застосовувати у вікні ROWS" -#: parser/parse_agg.c:424 +#: parser/parse_agg.c:435 msgid "aggregate functions are not allowed in window GROUPS" msgstr "агрегатні функції не можна застосовувати у вікні GROUPS" -#: parser/parse_agg.c:426 +#: parser/parse_agg.c:437 msgid "grouping operations are not allowed in window GROUPS" msgstr "операції групування не можна застосовувати у вікні GROUPS" -#: parser/parse_agg.c:460 +#: parser/parse_agg.c:471 msgid "aggregate functions are not allowed in check constraints" msgstr "агрегатні функції не можна застосовувати в перевірці обмежень" -#: parser/parse_agg.c:462 +#: parser/parse_agg.c:473 msgid "grouping operations are not allowed in check constraints" msgstr "операції групування не можна застосовувати в перевірці обмежень" -#: parser/parse_agg.c:469 +#: parser/parse_agg.c:480 msgid "aggregate functions are not allowed in DEFAULT expressions" msgstr "агрегатні функції не можна застосовувати у виразах DEFAULT" -#: parser/parse_agg.c:471 +#: parser/parse_agg.c:482 msgid "grouping operations are not allowed in DEFAULT expressions" msgstr "операції групування не можна застосовувати у виразах DEFAULT" -#: parser/parse_agg.c:476 +#: parser/parse_agg.c:487 msgid "aggregate functions are not allowed in index expressions" msgstr "агрегатні функції не можна застосовувати у виразах індексів" -#: parser/parse_agg.c:478 +#: parser/parse_agg.c:489 msgid "grouping operations are not allowed in index expressions" msgstr "операції групування не можна застосовувати у виразах індексів" -#: parser/parse_agg.c:483 +#: parser/parse_agg.c:494 msgid "aggregate functions are not allowed in index predicates" msgstr "агрегатні функції не можна застосовувати в предикатах індексів" -#: parser/parse_agg.c:485 +#: parser/parse_agg.c:496 msgid "grouping operations are not allowed in index predicates" msgstr "операції групування не можна застосовувати в предикатах індексів" -#: parser/parse_agg.c:490 +#: parser/parse_agg.c:501 msgid "aggregate functions are not allowed in transform expressions" msgstr "агрегатні функції не можна застосовувати у виразах перетворювання" -#: parser/parse_agg.c:492 +#: parser/parse_agg.c:503 msgid "grouping operations are not allowed in transform expressions" msgstr "операції групування не можна застосовувати у виразах перетворювання" -#: parser/parse_agg.c:497 +#: parser/parse_agg.c:508 msgid "aggregate functions are not allowed in EXECUTE parameters" msgstr "агрегатні функції не можна застосовувати в параметрах EXECUTE" -#: parser/parse_agg.c:499 +#: parser/parse_agg.c:510 msgid "grouping operations are not allowed in EXECUTE parameters" msgstr "операції групування не можна застосовувати в параметрах EXECUTE" -#: parser/parse_agg.c:504 +#: parser/parse_agg.c:515 msgid "aggregate functions are not allowed in trigger WHEN conditions" msgstr "агрегатні функції не можна застосовувати в умовах для тригерів WHEN" -#: parser/parse_agg.c:506 +#: parser/parse_agg.c:517 msgid "grouping operations are not allowed in trigger WHEN conditions" msgstr "операції групування не можна застосовувати в умовах для тригерів WHEN" -#: parser/parse_agg.c:511 +#: parser/parse_agg.c:522 msgid "aggregate functions are not allowed in partition bound" msgstr "агрегатні функції не можна застосовувати в границі секції" -#: parser/parse_agg.c:513 +#: parser/parse_agg.c:524 msgid "grouping operations are not allowed in partition bound" msgstr "операції групування не можна застосовувати в границі секції" -#: parser/parse_agg.c:518 +#: parser/parse_agg.c:529 msgid "aggregate functions are not allowed in partition key expressions" msgstr "агрегатні функції не можна застосовувати у виразах ключа секціонування" -#: parser/parse_agg.c:520 +#: parser/parse_agg.c:531 msgid "grouping operations are not allowed in partition key expressions" msgstr "операції групування не можна застосовувати у виразах ключа секціонування" -#: parser/parse_agg.c:526 +#: parser/parse_agg.c:537 msgid "aggregate functions are not allowed in column generation expressions" msgstr "агрегатні функції не можна застосовувати у виразах генерації стовпців" -#: parser/parse_agg.c:528 +#: parser/parse_agg.c:539 msgid "grouping operations are not allowed in column generation expressions" msgstr "операції групування не можна застосовувати у виразах генерації стовпців" -#: parser/parse_agg.c:534 +#: parser/parse_agg.c:545 msgid "aggregate functions are not allowed in CALL arguments" msgstr "агрегатні функції не можна застосовувати в аргументах CALL" -#: parser/parse_agg.c:536 +#: parser/parse_agg.c:547 msgid "grouping operations are not allowed in CALL arguments" msgstr "операції групування не можна застосовувати в аргументах CALL" -#: parser/parse_agg.c:542 +#: parser/parse_agg.c:553 msgid "aggregate functions are not allowed in COPY FROM WHERE conditions" msgstr "агрегатні функції не можна застосовувати в умовах COPY FROM WHERE" -#: parser/parse_agg.c:544 +#: parser/parse_agg.c:555 msgid "grouping operations are not allowed in COPY FROM WHERE conditions" msgstr "операції групування не можна застосовувати в умовах COPY FROM WHERE" #. translator: %s is name of a SQL construct, eg GROUP BY -#: parser/parse_agg.c:567 parser/parse_clause.c:1816 +#: parser/parse_agg.c:578 parser/parse_clause.c:1816 #, c-format msgid "aggregate functions are not allowed in %s" msgstr "агрегатні функції не можна застосовувати в %s" #. translator: %s is name of a SQL construct, eg GROUP BY -#: parser/parse_agg.c:570 +#: parser/parse_agg.c:581 #, c-format msgid "grouping operations are not allowed in %s" msgstr "операції групування не можна застосовувати в %s" -#: parser/parse_agg.c:671 +#: parser/parse_agg.c:682 #, c-format msgid "outer-level aggregate cannot contain a lower-level variable in its direct arguments" msgstr "агрегат зовнішнього рівня не може містити змінну нижчого рівня у своїх аргументах" -#: parser/parse_agg.c:749 +#: parser/parse_agg.c:760 #, c-format msgid "aggregate function calls cannot contain set-returning function calls" msgstr "виклики агрегатної функції не можуть містити викликів функції, що повертають множину" -#: parser/parse_agg.c:750 parser/parse_expr.c:1850 parser/parse_expr.c:2345 +#: parser/parse_agg.c:761 parser/parse_expr.c:1850 parser/parse_expr.c:2345 #: parser/parse_func.c:872 #, c-format msgid "You might be able to move the set-returning function into a LATERAL FROM item." msgstr "Можливо перемістити функцію, що повертає множину, в елемент LATERAL FROM." -#: parser/parse_agg.c:755 +#: parser/parse_agg.c:766 #, c-format msgid "aggregate function calls cannot contain window function calls" msgstr "виклики агрегатних функцій не можуть містити виклики віконних функцій" -#: parser/parse_agg.c:834 +#: parser/parse_agg.c:845 msgid "window functions are not allowed in JOIN conditions" msgstr "віконні функції не можна застосовувати в умовах JOIN" -#: parser/parse_agg.c:841 +#: parser/parse_agg.c:852 msgid "window functions are not allowed in functions in FROM" msgstr "віконні функції не можна застосовувати у функціях в FROM" -#: parser/parse_agg.c:847 +#: parser/parse_agg.c:858 msgid "window functions are not allowed in policy expressions" msgstr "віконні функції не можна застосовувати у виразах політики" -#: parser/parse_agg.c:860 +#: parser/parse_agg.c:871 msgid "window functions are not allowed in window definitions" msgstr "віконні функції не можна застосовувати у визначенні вікна" -#: parser/parse_agg.c:892 +#: parser/parse_agg.c:903 msgid "window functions are not allowed in check constraints" msgstr "віконні функції не можна застосовувати в перевірках обмежень" -#: parser/parse_agg.c:896 +#: parser/parse_agg.c:907 msgid "window functions are not allowed in DEFAULT expressions" msgstr "віконні функції не можна застосовувати у виразах DEFAULT" -#: parser/parse_agg.c:899 +#: parser/parse_agg.c:910 msgid "window functions are not allowed in index expressions" msgstr "віконні функції не можна застосовувати у виразах індексів" -#: parser/parse_agg.c:902 +#: parser/parse_agg.c:913 msgid "window functions are not allowed in index predicates" msgstr "віконні функції не можна застосовувати в предикатах індексів" -#: parser/parse_agg.c:905 +#: parser/parse_agg.c:916 msgid "window functions are not allowed in transform expressions" msgstr "віконні функції не можна застосовувати у виразах перетворювання" -#: parser/parse_agg.c:908 +#: parser/parse_agg.c:919 msgid "window functions are not allowed in EXECUTE parameters" msgstr "віконні функції не можна застосовувати в параметрах EXECUTE" -#: parser/parse_agg.c:911 +#: parser/parse_agg.c:922 msgid "window functions are not allowed in trigger WHEN conditions" msgstr "віконні функції не можна застосовувати в умовах WHEN для тригерів" -#: parser/parse_agg.c:914 +#: parser/parse_agg.c:925 msgid "window functions are not allowed in partition bound" msgstr "віконні функції не можна застосовувати в границі секції" -#: parser/parse_agg.c:917 +#: parser/parse_agg.c:928 msgid "window functions are not allowed in partition key expressions" msgstr "віконні функції не можна застосовувати у виразах ключа секціонування" -#: parser/parse_agg.c:920 +#: parser/parse_agg.c:931 msgid "window functions are not allowed in CALL arguments" msgstr "віконні функції не можна застосовувати в аргументах CALL" -#: parser/parse_agg.c:923 +#: parser/parse_agg.c:934 msgid "window functions are not allowed in COPY FROM WHERE conditions" msgstr "віконні функції не можна застосовувати в умовах COPY FROM WHERE" -#: parser/parse_agg.c:926 +#: parser/parse_agg.c:937 msgid "window functions are not allowed in column generation expressions" msgstr "віконні функції не можна застосовувати у виразах генерації стовпців" #. translator: %s is name of a SQL construct, eg GROUP BY -#: parser/parse_agg.c:946 parser/parse_clause.c:1825 +#: parser/parse_agg.c:957 parser/parse_clause.c:1825 #, c-format msgid "window functions are not allowed in %s" msgstr "віконні функції не можна застосовувати в %s" -#: parser/parse_agg.c:980 parser/parse_clause.c:2659 +#: parser/parse_agg.c:991 parser/parse_clause.c:2659 #, c-format msgid "window \"%s\" does not exist" msgstr "вікно \"%s\" не існує" -#: parser/parse_agg.c:1064 +#: parser/parse_agg.c:1075 #, c-format msgid "too many grouping sets present (maximum 4096)" msgstr "забагато наборів групування (максимум 4096)" -#: parser/parse_agg.c:1204 +#: parser/parse_agg.c:1215 #, c-format msgid "aggregate functions are not allowed in a recursive query's recursive term" msgstr "агрегатні функції не дозволені у рекурсивному терміні рекурсивного запиту" -#: parser/parse_agg.c:1397 +#: parser/parse_agg.c:1408 #, c-format msgid "column \"%s.%s\" must appear in the GROUP BY clause or be used in an aggregate function" msgstr "стовпець \"%s.%s\" повинен з'являтися у реченні Група BY або використовуватися в агрегатній функції" -#: parser/parse_agg.c:1400 +#: parser/parse_agg.c:1411 #, c-format msgid "Direct arguments of an ordered-set aggregate must use only grouped columns." msgstr "Прямі аргументи сортувального агрегату можуть використовувати лише згруповані стовпці." -#: parser/parse_agg.c:1405 +#: parser/parse_agg.c:1416 #, c-format msgid "subquery uses ungrouped column \"%s.%s\" from outer query" msgstr "вкладений запит використовує не згруповані стовпці \"%s.%s\" з зовнішнього запиту" -#: parser/parse_agg.c:1569 +#: parser/parse_agg.c:1580 #, c-format msgid "arguments to GROUPING must be grouping expressions of the associated query level" msgstr "аргументами групування мають бути вирази групування пов'язаного рівня запиту" @@ -15274,7 +15278,7 @@ msgstr "аргументи, оголошенні як \"anyrange\", повинні бути схожими" #: parser/parse_coerce.c:2087 parser/parse_coerce.c:2167 -#: utils/fmgr/funcapi.c:487 +#: utils/fmgr/funcapi.c:521 #, c-format msgid "argument declared %s is not an array but type %s" msgstr "аргумент, оголошений як %s , є не масивом, а типом %s" @@ -15285,7 +15289,7 @@ msgstr "аргументи, оголошенні як \"anycompatiblerange\", повинні бути схожими" #: parser/parse_coerce.c:2120 parser/parse_coerce.c:2201 -#: utils/fmgr/funcapi.c:501 +#: utils/fmgr/funcapi.c:535 #, c-format msgid "argument declared %s is not a range type but type %s" msgstr "аргумент, оголошений як %s, є не діапазонним типом, а типом %s" @@ -16304,8 +16308,8 @@ msgid "type reference %s converted to %s" msgstr "посилання на тип %s перетворене на тип %s" -#: parser/parse_type.c:278 parser/parse_type.c:857 utils/cache/typcache.c:383 -#: utils/cache/typcache.c:437 +#: parser/parse_type.c:278 parser/parse_type.c:857 utils/cache/typcache.c:388 +#: utils/cache/typcache.c:442 #, c-format msgid "type \"%s\" is only a shell" msgstr "тип \"%s\" є лише оболонкою" @@ -16436,11 +16440,6 @@ msgid "index \"%s\" is already associated with a constraint" msgstr "індекс \"%s\" вже пов'язаний з обмеженням" -#: parser/parse_utilcmd.c:2243 -#, c-format -msgid "index \"%s\" is not valid" -msgstr "індекс \"%s\" не є припустимим" - #: parser/parse_utilcmd.c:2249 #, c-format msgid "\"%s\" is not a unique index" @@ -16808,12 +16807,12 @@ msgid "huge pages not supported with the current shared_memory_type setting" msgstr "величезні сторінки не підтримуються з поточним параметром shared_memory_type" -#: port/pg_shmem.c:725 port/sysv_shmem.c:725 utils/init/miscinit.c:1142 +#: port/pg_shmem.c:725 port/sysv_shmem.c:725 utils/init/miscinit.c:1150 #, c-format msgid "pre-existing shared memory block (key %lu, ID %lu) is still in use" msgstr "раніше виділений блок спільної пам'яті (ключ %lu, ідентифікатор %lu) все ще використовується" -#: port/pg_shmem.c:728 port/sysv_shmem.c:728 utils/init/miscinit.c:1144 +#: port/pg_shmem.c:728 port/sysv_shmem.c:728 utils/init/miscinit.c:1152 #, c-format msgid "Terminate any old server processes associated with data directory \"%s\"." msgstr "Припинити будь-які старі серверні процеси, пов'язані з каталогом даних \"%s\"." @@ -17146,7 +17145,7 @@ msgid "archive command was terminated by exception 0x%X" msgstr "команда архівації була перервана винятком 0x%X" -#: postmaster/pgarch.c:605 postmaster/postmaster.c:3756 +#: postmaster/pgarch.c:605 postmaster/postmaster.c:3759 #, c-format msgid "See C include file \"ntstatus.h\" for a description of the hexadecimal value." msgstr "Опис цього Шістнадцяткового значення дивіться у включаємому C-файлі \"ntstatus.h\"." @@ -17241,53 +17240,53 @@ msgid "Target must be \"archiver\" or \"bgwriter\"." msgstr "Мета повинна бути \"archiver\" або \"bgwriter\"." -#: postmaster/pgstat.c:4570 +#: postmaster/pgstat.c:4571 #, c-format msgid "could not read statistics message: %m" msgstr "не вдалося прочитати повідомлення статистики: %m" -#: postmaster/pgstat.c:4892 postmaster/pgstat.c:5055 +#: postmaster/pgstat.c:4893 postmaster/pgstat.c:5056 #, c-format msgid "could not open temporary statistics file \"%s\": %m" msgstr "не вдалося відкрити тимчасовий файл статистики \"%s\": %m" -#: postmaster/pgstat.c:4965 postmaster/pgstat.c:5100 +#: postmaster/pgstat.c:4966 postmaster/pgstat.c:5101 #, c-format msgid "could not write temporary statistics file \"%s\": %m" msgstr "не вдалося записати в тимчасовий файл статистики \"%s\": %m" -#: postmaster/pgstat.c:4974 postmaster/pgstat.c:5109 +#: postmaster/pgstat.c:4975 postmaster/pgstat.c:5110 #, c-format msgid "could not close temporary statistics file \"%s\": %m" msgstr "не вдалося закрити тимчасовий файл статистики \"%s\": %m" -#: postmaster/pgstat.c:4982 postmaster/pgstat.c:5117 +#: postmaster/pgstat.c:4983 postmaster/pgstat.c:5118 #, c-format msgid "could not rename temporary statistics file \"%s\" to \"%s\": %m" msgstr "не вдалося перейменувати тимчасовий файл статистики з \"%s\" в \"%s\": %m" -#: postmaster/pgstat.c:5214 postmaster/pgstat.c:5431 postmaster/pgstat.c:5585 +#: postmaster/pgstat.c:5215 postmaster/pgstat.c:5432 postmaster/pgstat.c:5586 #, c-format msgid "could not open statistics file \"%s\": %m" msgstr "не вдалося відкрити файл статистики \"%s\": %m" -#: postmaster/pgstat.c:5226 postmaster/pgstat.c:5236 postmaster/pgstat.c:5257 -#: postmaster/pgstat.c:5268 postmaster/pgstat.c:5290 postmaster/pgstat.c:5305 -#: postmaster/pgstat.c:5368 postmaster/pgstat.c:5443 postmaster/pgstat.c:5463 -#: postmaster/pgstat.c:5481 postmaster/pgstat.c:5497 postmaster/pgstat.c:5515 -#: postmaster/pgstat.c:5531 postmaster/pgstat.c:5597 postmaster/pgstat.c:5609 -#: postmaster/pgstat.c:5621 postmaster/pgstat.c:5632 postmaster/pgstat.c:5657 -#: postmaster/pgstat.c:5679 +#: postmaster/pgstat.c:5227 postmaster/pgstat.c:5237 postmaster/pgstat.c:5258 +#: postmaster/pgstat.c:5269 postmaster/pgstat.c:5291 postmaster/pgstat.c:5306 +#: postmaster/pgstat.c:5369 postmaster/pgstat.c:5444 postmaster/pgstat.c:5464 +#: postmaster/pgstat.c:5482 postmaster/pgstat.c:5498 postmaster/pgstat.c:5516 +#: postmaster/pgstat.c:5532 postmaster/pgstat.c:5598 postmaster/pgstat.c:5610 +#: postmaster/pgstat.c:5622 postmaster/pgstat.c:5633 postmaster/pgstat.c:5658 +#: postmaster/pgstat.c:5680 #, c-format msgid "corrupted statistics file \"%s\"" msgstr "пошкоджений файл статистики \"%s\"" -#: postmaster/pgstat.c:5808 +#: postmaster/pgstat.c:5809 #, c-format msgid "using stale statistics instead of current ones because stats collector is not responding" msgstr "використовується застаріла статистика замість поточної, тому, що збирач статистики не відповідає" -#: postmaster/pgstat.c:6138 +#: postmaster/pgstat.c:6139 #, c-format msgid "database hash table corrupted during cleanup --- abort" msgstr "таблиця гешування бази даних пошкоджена під час очищення --- переривання" @@ -17332,88 +17331,88 @@ msgid "could not create I/O completion port for child queue" msgstr "не вдалося створити завершений порт вводу-виводу для черги дітей" -#: postmaster/postmaster.c:1113 +#: postmaster/postmaster.c:1124 #, c-format msgid "ending log output to stderr" msgstr "завершення запису виводу Stderr" -#: postmaster/postmaster.c:1114 +#: postmaster/postmaster.c:1125 #, c-format msgid "Future log output will go to log destination \"%s\"." msgstr "В майбутньому запис виведення буде записуватися в призначення \"%s\"." -#: postmaster/postmaster.c:1125 +#: postmaster/postmaster.c:1136 #, c-format msgid "starting %s" msgstr "початок %s" -#: postmaster/postmaster.c:1154 postmaster/postmaster.c:1252 -#: utils/init/miscinit.c:1602 +#: postmaster/postmaster.c:1157 postmaster/postmaster.c:1255 +#: utils/init/miscinit.c:1610 #, c-format msgid "invalid list syntax in parameter \"%s\"" msgstr "неприпустимий синтаксис списку в параметрі \"%s\"" -#: postmaster/postmaster.c:1185 +#: postmaster/postmaster.c:1188 #, c-format msgid "could not create listen socket for \"%s\"" msgstr "не вдалося створити сокет прослуховування для \"%s\"" -#: postmaster/postmaster.c:1191 +#: postmaster/postmaster.c:1194 #, c-format msgid "could not create any TCP/IP sockets" msgstr "не вдалося створити TCP/IP сокети" -#: postmaster/postmaster.c:1274 +#: postmaster/postmaster.c:1277 #, c-format msgid "could not create Unix-domain socket in directory \"%s\"" msgstr "не вдалося створити Unix-domain сокет в каталозі \"%s\"" -#: postmaster/postmaster.c:1280 +#: postmaster/postmaster.c:1283 #, c-format msgid "could not create any Unix-domain sockets" msgstr "не вдалося створити Unix-domain сокети" -#: postmaster/postmaster.c:1292 +#: postmaster/postmaster.c:1295 #, c-format msgid "no socket created for listening" msgstr "не створено жодного сокету для прослуховування" -#: postmaster/postmaster.c:1323 +#: postmaster/postmaster.c:1326 #, c-format msgid "%s: could not change permissions of external PID file \"%s\": %s\n" msgstr "%s: не вдалося змінити дозволи зовнішнього PID файлу \"%s\": %s\n" -#: postmaster/postmaster.c:1327 +#: postmaster/postmaster.c:1330 #, c-format msgid "%s: could not write external PID file \"%s\": %s\n" msgstr "%s: не вдалося записати зовнішній PID файл \"%s\": %s\n" -#: postmaster/postmaster.c:1360 utils/init/postinit.c:215 +#: postmaster/postmaster.c:1363 utils/init/postinit.c:215 #, c-format msgid "could not load pg_hba.conf" msgstr "не вдалося завантажити pg_hba.conf" -#: postmaster/postmaster.c:1386 +#: postmaster/postmaster.c:1389 #, c-format msgid "postmaster became multithreaded during startup" msgstr "адміністратор поштового сервера став багатопотоковим під час запуску" -#: postmaster/postmaster.c:1387 +#: postmaster/postmaster.c:1390 #, c-format msgid "Set the LC_ALL environment variable to a valid locale." msgstr "Встановити в змінній середовища LC_ALL дійісну локаль." -#: postmaster/postmaster.c:1488 +#: postmaster/postmaster.c:1491 #, c-format msgid "%s: could not locate matching postgres executable" msgstr "%s: не вдалося знайти відповідний postgres файл, що виконується" -#: postmaster/postmaster.c:1511 utils/misc/tzparser.c:340 +#: postmaster/postmaster.c:1514 utils/misc/tzparser.c:340 #, c-format msgid "This may indicate an incomplete PostgreSQL installation, or that the file \"%s\" has been moved away from its proper location." msgstr "Це може означати неповне встановлення PostgreSQL, або те, що файл \"%s\" було переміщено з його правильного розташування." -#: postmaster/postmaster.c:1538 +#: postmaster/postmaster.c:1541 #, c-format msgid "%s: could not find the database system\n" "Expected to find it in the directory \"%s\",\n" @@ -17422,411 +17421,411 @@ "Очікувалося знайти її у каталозі \"%s\",\n" "але не вдалося відкрити файл \"%s\": %s\n" -#: postmaster/postmaster.c:1715 +#: postmaster/postmaster.c:1718 #, c-format msgid "select() failed in postmaster: %m" msgstr "помилка вибирати() в адміністраторі поштового сервера: %m" -#: postmaster/postmaster.c:1870 +#: postmaster/postmaster.c:1873 #, c-format msgid "performing immediate shutdown because data directory lock file is invalid" msgstr "виконується негайне припинення роботи через неприпустимий файл блокування каталогу даних" -#: postmaster/postmaster.c:1973 postmaster/postmaster.c:2004 +#: postmaster/postmaster.c:1976 postmaster/postmaster.c:2007 #, c-format msgid "incomplete startup packet" msgstr "неповний стартовий пакет" -#: postmaster/postmaster.c:1985 postmaster/postmaster.c:2021 +#: postmaster/postmaster.c:1988 postmaster/postmaster.c:2024 #, c-format msgid "invalid length of startup packet" msgstr "неприпустима довжина стартового пакету" -#: postmaster/postmaster.c:2050 +#: postmaster/postmaster.c:2053 #, c-format msgid "failed to send SSL negotiation response: %m" msgstr "помилка надсилання протоколу SSL в процесі відповіді зв'язування: %m" -#: postmaster/postmaster.c:2068 +#: postmaster/postmaster.c:2071 #, c-format msgid "received unencrypted data after SSL request" msgstr "отримані незашифровані дані після запиту SSL" -#: postmaster/postmaster.c:2069 postmaster/postmaster.c:2113 +#: postmaster/postmaster.c:2072 postmaster/postmaster.c:2116 #, c-format msgid "This could be either a client-software bug or evidence of an attempted man-in-the-middle attack." msgstr "Це може бути або помилкою клієнтського програмного забезпечення, або доказом спроби техносферної атаки." -#: postmaster/postmaster.c:2094 +#: postmaster/postmaster.c:2097 #, c-format msgid "failed to send GSSAPI negotiation response: %m" msgstr "помилка надсилання GSSAPI в процесі відповіді зв'язування: %m" -#: postmaster/postmaster.c:2112 +#: postmaster/postmaster.c:2115 #, c-format msgid "received unencrypted data after GSSAPI encryption request" msgstr "отримані незашифровані дані після запиту шифрування GSSAPI" -#: postmaster/postmaster.c:2136 +#: postmaster/postmaster.c:2139 #, c-format msgid "unsupported frontend protocol %u.%u: server supports %u.0 to %u.%u" msgstr "протокол інтерфейсу, що не підтримується, %u.%u: сервер підтримує %u.0 до %u.%u" -#: postmaster/postmaster.c:2200 utils/misc/guc.c:6781 utils/misc/guc.c:6817 -#: utils/misc/guc.c:6887 utils/misc/guc.c:8238 utils/misc/guc.c:11110 -#: utils/misc/guc.c:11151 +#: postmaster/postmaster.c:2203 utils/misc/guc.c:6781 utils/misc/guc.c:6817 +#: utils/misc/guc.c:6887 utils/misc/guc.c:8238 utils/misc/guc.c:11118 +#: utils/misc/guc.c:11159 #, c-format msgid "invalid value for parameter \"%s\": \"%s\"" msgstr "неприпустиме значення параметру \"%s\": \"%s\"" -#: postmaster/postmaster.c:2203 +#: postmaster/postmaster.c:2206 #, c-format msgid "Valid values are: \"false\", 0, \"true\", 1, \"database\"." msgstr "Дійсні значення: \"false\", 0, \"true\", 1, \"database\"." -#: postmaster/postmaster.c:2248 +#: postmaster/postmaster.c:2251 #, c-format msgid "invalid startup packet layout: expected terminator as last byte" msgstr "неприпустима структура стартового пакету: останнім байтом очікувався термінатор" -#: postmaster/postmaster.c:2286 +#: postmaster/postmaster.c:2289 #, c-format msgid "no PostgreSQL user name specified in startup packet" msgstr "не вказано жодного ім'я користувача PostgreSQL у стартовому пакеті" -#: postmaster/postmaster.c:2350 +#: postmaster/postmaster.c:2353 #, c-format msgid "the database system is starting up" msgstr "система бази даних запускається" -#: postmaster/postmaster.c:2355 +#: postmaster/postmaster.c:2358 #, c-format msgid "the database system is shutting down" msgstr "система бази даних завершує роботу" -#: postmaster/postmaster.c:2360 +#: postmaster/postmaster.c:2363 #, c-format msgid "the database system is in recovery mode" msgstr "система бази даних у режимі відновлення" -#: postmaster/postmaster.c:2365 storage/ipc/procarray.c:314 +#: postmaster/postmaster.c:2368 storage/ipc/procarray.c:314 #: storage/ipc/sinvaladt.c:297 storage/lmgr/proc.c:362 #, c-format msgid "sorry, too many clients already" msgstr "вибачте, вже забагато клієнтів" -#: postmaster/postmaster.c:2455 +#: postmaster/postmaster.c:2458 #, c-format msgid "wrong key in cancel request for process %d" msgstr "неправильний ключ в запиті скасування процесу %d" -#: postmaster/postmaster.c:2467 +#: postmaster/postmaster.c:2470 #, c-format msgid "PID %d in cancel request did not match any process" msgstr "PID %d в запиті на скасування не відповідає жодному процесу" -#: postmaster/postmaster.c:2720 +#: postmaster/postmaster.c:2723 #, c-format msgid "received SIGHUP, reloading configuration files" msgstr "отримано SIGHUP, поновлення файлів конфігурацій" #. translator: %s is a configuration file -#: postmaster/postmaster.c:2746 postmaster/postmaster.c:2750 +#: postmaster/postmaster.c:2749 postmaster/postmaster.c:2753 #, c-format msgid "%s was not reloaded" msgstr "%s не було перезавантажено" -#: postmaster/postmaster.c:2760 +#: postmaster/postmaster.c:2763 #, c-format msgid "SSL configuration was not reloaded" msgstr "Конфігурація протоколу SSL не була перезавантажена" -#: postmaster/postmaster.c:2816 +#: postmaster/postmaster.c:2819 #, c-format msgid "received smart shutdown request" msgstr "отримано smart запит на завершення роботи" -#: postmaster/postmaster.c:2862 +#: postmaster/postmaster.c:2865 #, c-format msgid "received fast shutdown request" msgstr "отримано швидкий запит на завершення роботи" -#: postmaster/postmaster.c:2880 +#: postmaster/postmaster.c:2883 #, c-format msgid "aborting any active transactions" msgstr "переривання будь-яких активних транзакцій" -#: postmaster/postmaster.c:2904 +#: postmaster/postmaster.c:2907 #, c-format msgid "received immediate shutdown request" msgstr "отримано запит на негайне завершення роботи" -#: postmaster/postmaster.c:2979 +#: postmaster/postmaster.c:2982 #, c-format msgid "shutdown at recovery target" msgstr "завершення роботи при відновленні мети" -#: postmaster/postmaster.c:2997 postmaster/postmaster.c:3033 +#: postmaster/postmaster.c:3000 postmaster/postmaster.c:3036 msgid "startup process" msgstr "стартовий процес" -#: postmaster/postmaster.c:3000 +#: postmaster/postmaster.c:3003 #, c-format msgid "aborting startup due to startup process failure" msgstr "переривання запуску через помилку в стартовому процесі" -#: postmaster/postmaster.c:3075 +#: postmaster/postmaster.c:3078 #, c-format msgid "database system is ready to accept connections" msgstr "система бази даних готова до отримання підключення" -#: postmaster/postmaster.c:3096 +#: postmaster/postmaster.c:3099 msgid "background writer process" msgstr "процес фонового запису" -#: postmaster/postmaster.c:3150 +#: postmaster/postmaster.c:3153 msgid "checkpointer process" msgstr "процес контрольних точок" -#: postmaster/postmaster.c:3166 +#: postmaster/postmaster.c:3169 msgid "WAL writer process" msgstr "Процес запису WAL" -#: postmaster/postmaster.c:3181 +#: postmaster/postmaster.c:3184 msgid "WAL receiver process" msgstr "Процес отримання WAL" -#: postmaster/postmaster.c:3196 +#: postmaster/postmaster.c:3199 msgid "autovacuum launcher process" msgstr "процес запуску автоочистки" -#: postmaster/postmaster.c:3211 +#: postmaster/postmaster.c:3214 msgid "archiver process" msgstr "процес архівації" -#: postmaster/postmaster.c:3227 +#: postmaster/postmaster.c:3230 msgid "statistics collector process" msgstr "процес збору статистики" -#: postmaster/postmaster.c:3241 +#: postmaster/postmaster.c:3244 msgid "system logger process" msgstr "процес системного журналювання" -#: postmaster/postmaster.c:3305 +#: postmaster/postmaster.c:3308 #, c-format msgid "background worker \"%s\"" msgstr "фоновий виконавець \"%s\"" -#: postmaster/postmaster.c:3389 postmaster/postmaster.c:3409 -#: postmaster/postmaster.c:3416 postmaster/postmaster.c:3434 +#: postmaster/postmaster.c:3392 postmaster/postmaster.c:3412 +#: postmaster/postmaster.c:3419 postmaster/postmaster.c:3437 msgid "server process" msgstr "процес сервера" -#: postmaster/postmaster.c:3488 +#: postmaster/postmaster.c:3491 #, c-format msgid "terminating any other active server processes" msgstr "завершення будь-яких інших активних серверних процесів" #. translator: %s is a noun phrase describing a child process, such as #. "server process" -#: postmaster/postmaster.c:3743 +#: postmaster/postmaster.c:3746 #, c-format msgid "%s (PID %d) exited with exit code %d" msgstr "%s (PID %d) завершився з кодом виходу %d" -#: postmaster/postmaster.c:3745 postmaster/postmaster.c:3757 -#: postmaster/postmaster.c:3767 postmaster/postmaster.c:3778 +#: postmaster/postmaster.c:3748 postmaster/postmaster.c:3760 +#: postmaster/postmaster.c:3770 postmaster/postmaster.c:3781 #, c-format msgid "Failed process was running: %s" msgstr "Процес що завершився виконував дію: %s" #. translator: %s is a noun phrase describing a child process, such as #. "server process" -#: postmaster/postmaster.c:3754 +#: postmaster/postmaster.c:3757 #, c-format msgid "%s (PID %d) was terminated by exception 0x%X" msgstr "%s (PID %d) був перерваний винятком 0x%X" #. translator: %s is a noun phrase describing a child process, such as #. "server process" -#: postmaster/postmaster.c:3764 +#: postmaster/postmaster.c:3767 #, c-format msgid "%s (PID %d) was terminated by signal %d: %s" msgstr "%s (PID %d) був перерваний сигналом %d: %s" #. translator: %s is a noun phrase describing a child process, such as #. "server process" -#: postmaster/postmaster.c:3776 +#: postmaster/postmaster.c:3779 #, c-format msgid "%s (PID %d) exited with unrecognized status %d" msgstr "%s (PID %d) завершився з нерозпізнаним статусом %d" -#: postmaster/postmaster.c:3991 +#: postmaster/postmaster.c:3994 #, c-format msgid "abnormal database system shutdown" msgstr "ненормальне завершення роботи системи бази даних" -#: postmaster/postmaster.c:4031 +#: postmaster/postmaster.c:4034 #, c-format msgid "all server processes terminated; reinitializing" msgstr "усі серверні процеси перервано; повторна ініціалізація" -#: postmaster/postmaster.c:4201 postmaster/postmaster.c:5602 -#: postmaster/postmaster.c:5989 +#: postmaster/postmaster.c:4204 postmaster/postmaster.c:5605 +#: postmaster/postmaster.c:5992 #, c-format msgid "could not generate random cancel key" msgstr "не вдалося згенерувати випадковий ключ скасування" -#: postmaster/postmaster.c:4255 +#: postmaster/postmaster.c:4258 #, c-format msgid "could not fork new process for connection: %m" msgstr "не вдалося породити нові процеси для з'єднання: %m" -#: postmaster/postmaster.c:4297 +#: postmaster/postmaster.c:4300 msgid "could not fork new process for connection: " msgstr "не вдалося породити нові процеси для з'єднання: " -#: postmaster/postmaster.c:4414 +#: postmaster/postmaster.c:4417 #, c-format msgid "connection received: host=%s port=%s" msgstr "з'єднання отримано: хост=%s порт=%s" -#: postmaster/postmaster.c:4419 +#: postmaster/postmaster.c:4422 #, c-format msgid "connection received: host=%s" msgstr "з'єднання отримано: хост=%s" -#: postmaster/postmaster.c:4689 +#: postmaster/postmaster.c:4692 #, c-format msgid "could not execute server process \"%s\": %m" msgstr "не вдалося виконати серверні процеси \"%s\":%m" -#: postmaster/postmaster.c:4848 +#: postmaster/postmaster.c:4851 #, c-format msgid "giving up after too many tries to reserve shared memory" msgstr "кількість повторних спроб резервування спільної пам'яті досягло межі" -#: postmaster/postmaster.c:4849 +#: postmaster/postmaster.c:4852 #, c-format msgid "This might be caused by ASLR or antivirus software." msgstr "Це може бути викликано антивірусним програмним забезпеченням або ASLR." -#: postmaster/postmaster.c:5035 +#: postmaster/postmaster.c:5038 #, c-format msgid "SSL configuration could not be loaded in child process" msgstr "Не вдалося завантажити конфігурацію SSL в дочірній процес" -#: postmaster/postmaster.c:5167 +#: postmaster/postmaster.c:5170 #, c-format msgid "Please report this to <%s>." msgstr "Будь-ласка повідомте про це <%s>." -#: postmaster/postmaster.c:5254 +#: postmaster/postmaster.c:5257 #, c-format msgid "database system is ready to accept read only connections" msgstr "система бази даних готова до отримання підключення \"лише читати\"" -#: postmaster/postmaster.c:5530 +#: postmaster/postmaster.c:5533 #, c-format msgid "could not fork startup process: %m" msgstr "не вдалося породити стартовий процес: %m" -#: postmaster/postmaster.c:5534 +#: postmaster/postmaster.c:5537 #, c-format msgid "could not fork background writer process: %m" msgstr "не вдалося породити фоновий процес запису: %m" -#: postmaster/postmaster.c:5538 +#: postmaster/postmaster.c:5541 #, c-format msgid "could not fork checkpointer process: %m" msgstr "не вдалося породити процес контрольних точок: %m" -#: postmaster/postmaster.c:5542 +#: postmaster/postmaster.c:5545 #, c-format msgid "could not fork WAL writer process: %m" msgstr "не вдалося породити процес запису WAL: %m" -#: postmaster/postmaster.c:5546 +#: postmaster/postmaster.c:5549 #, c-format msgid "could not fork WAL receiver process: %m" msgstr "не вдалося породити процес отримання WAL: %m" -#: postmaster/postmaster.c:5550 +#: postmaster/postmaster.c:5553 #, c-format msgid "could not fork process: %m" msgstr "не вдалося породити процес: %m" -#: postmaster/postmaster.c:5747 postmaster/postmaster.c:5770 +#: postmaster/postmaster.c:5750 postmaster/postmaster.c:5773 #, c-format msgid "database connection requirement not indicated during registration" msgstr "під час реєстрації не вказувалося, що вимагається підключення до бази даних" -#: postmaster/postmaster.c:5754 postmaster/postmaster.c:5777 +#: postmaster/postmaster.c:5757 postmaster/postmaster.c:5780 #, c-format msgid "invalid processing mode in background worker" msgstr "неприпустимий режим обробки у фоновому записі" -#: postmaster/postmaster.c:5850 +#: postmaster/postmaster.c:5853 #, c-format msgid "starting background worker process \"%s\"" msgstr "початок процесу фонового запису \"%s\"" -#: postmaster/postmaster.c:5862 +#: postmaster/postmaster.c:5865 #, c-format msgid "could not fork worker process: %m" msgstr "не вдалося породити процес запису: %m" -#: postmaster/postmaster.c:5975 +#: postmaster/postmaster.c:5978 #, c-format msgid "no slot available for new worker process" msgstr "немає доступного слоту для нового робочого процесу" -#: postmaster/postmaster.c:6310 +#: postmaster/postmaster.c:6313 #, c-format msgid "could not duplicate socket %d for use in backend: error code %d" msgstr "не вдалося продублювати сокет %d для використання: код помилки %d" -#: postmaster/postmaster.c:6342 +#: postmaster/postmaster.c:6345 #, c-format msgid "could not create inherited socket: error code %d\n" msgstr "не вдалося створити успадкований сокет: код помилки %d\n" -#: postmaster/postmaster.c:6371 +#: postmaster/postmaster.c:6374 #, c-format msgid "could not open backend variables file \"%s\": %s\n" msgstr "не вдалося відкрити внутрішні змінні файли \"%s\": %s\n" -#: postmaster/postmaster.c:6378 +#: postmaster/postmaster.c:6381 #, c-format msgid "could not read from backend variables file \"%s\": %s\n" msgstr "не вдалося прочитати внутрішні змінні файли \"%s\": %s\n" -#: postmaster/postmaster.c:6387 +#: postmaster/postmaster.c:6390 #, c-format msgid "could not remove file \"%s\": %s\n" msgstr "не вдалося видалити файл \"%s\": %s\n" -#: postmaster/postmaster.c:6404 +#: postmaster/postmaster.c:6407 #, c-format msgid "could not map view of backend variables: error code %lu\n" msgstr "не вдалося відобразити файл серверних змінних: код помилки %lu\n" -#: postmaster/postmaster.c:6413 +#: postmaster/postmaster.c:6416 #, c-format msgid "could not unmap view of backend variables: error code %lu\n" msgstr "не вдалося вимкнути відображення файлу серверних змінних: код помилки %lu\n" -#: postmaster/postmaster.c:6420 +#: postmaster/postmaster.c:6423 #, c-format msgid "could not close handle to backend parameter variables: error code %lu\n" msgstr "не вдалося закрити покажчик файлу серверних змінних: код помилки %lu\n" -#: postmaster/postmaster.c:6583 +#: postmaster/postmaster.c:6586 #, c-format msgid "could not read exit code for process\n" msgstr "не вдалося прочитати код завершення процесу\n" -#: postmaster/postmaster.c:6625 +#: postmaster/postmaster.c:6628 #, c-format msgid "could not post child completion status\n" msgstr "не вдалося надіслати статус завершення нащадка\n" @@ -18064,93 +18063,93 @@ msgid "could not receive database system identifier and timeline ID from the primary server: %s" msgstr "не вдалося отримати ідентифікатор системи бази даних та ідентифікатор часової шкали з основного серверу: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:368 -#: replication/libpqwalreceiver/libpqwalreceiver.c:586 +#: replication/libpqwalreceiver/libpqwalreceiver.c:372 +#: replication/libpqwalreceiver/libpqwalreceiver.c:590 #, c-format msgid "invalid response from primary server" msgstr "неприпустима відповідь з основного серверу" -#: replication/libpqwalreceiver/libpqwalreceiver.c:369 +#: replication/libpqwalreceiver/libpqwalreceiver.c:373 #, c-format msgid "Could not identify system: got %d rows and %d fields, expected %d rows and %d or more fields." msgstr "Не вдалося ідентифікувати систему: отримано %d рядків і %d полів, очікувалось %d рядків і %d або більше полів." -#: replication/libpqwalreceiver/libpqwalreceiver.c:442 -#: replication/libpqwalreceiver/libpqwalreceiver.c:448 -#: replication/libpqwalreceiver/libpqwalreceiver.c:473 +#: replication/libpqwalreceiver/libpqwalreceiver.c:446 +#: replication/libpqwalreceiver/libpqwalreceiver.c:452 +#: replication/libpqwalreceiver/libpqwalreceiver.c:477 #, c-format msgid "could not start WAL streaming: %s" msgstr "не вдалося почати потокове передавання WAL: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:496 +#: replication/libpqwalreceiver/libpqwalreceiver.c:500 #, c-format msgid "could not send end-of-streaming message to primary: %s" msgstr "не вдалося передати основному серверу повідомлення про кінець передвання: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:518 +#: replication/libpqwalreceiver/libpqwalreceiver.c:522 #, c-format msgid "unexpected result set after end-of-streaming" msgstr "неочікуваний набір результатів після кінця передачі" -#: replication/libpqwalreceiver/libpqwalreceiver.c:532 +#: replication/libpqwalreceiver/libpqwalreceiver.c:536 #, c-format msgid "error while shutting down streaming COPY: %s" msgstr "помилка при завершенні потокового передавання \"копіювати\": %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:541 +#: replication/libpqwalreceiver/libpqwalreceiver.c:545 #, c-format msgid "error reading result of streaming command: %s" msgstr "помилка при читанні результату команди потокового передавання: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:549 -#: replication/libpqwalreceiver/libpqwalreceiver.c:783 +#: replication/libpqwalreceiver/libpqwalreceiver.c:553 +#: replication/libpqwalreceiver/libpqwalreceiver.c:787 #, c-format msgid "unexpected result after CommandComplete: %s" msgstr "неочікуваний результат CommandComplete: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:575 +#: replication/libpqwalreceiver/libpqwalreceiver.c:579 #, c-format msgid "could not receive timeline history file from the primary server: %s" msgstr "не вдалося отримати файл історії часової шкали з основного сервера: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:587 +#: replication/libpqwalreceiver/libpqwalreceiver.c:591 #, c-format msgid "Expected 1 tuple with 2 fields, got %d tuples with %d fields." msgstr "Очікувалося 1 кортеж з 2 поле, отримано %d кортежів з %d полями." -#: replication/libpqwalreceiver/libpqwalreceiver.c:747 -#: replication/libpqwalreceiver/libpqwalreceiver.c:798 -#: replication/libpqwalreceiver/libpqwalreceiver.c:804 +#: replication/libpqwalreceiver/libpqwalreceiver.c:751 +#: replication/libpqwalreceiver/libpqwalreceiver.c:802 +#: replication/libpqwalreceiver/libpqwalreceiver.c:808 #, c-format msgid "could not receive data from WAL stream: %s" msgstr "не вдалося отримати дані з WAL потоку: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:823 +#: replication/libpqwalreceiver/libpqwalreceiver.c:827 #, c-format msgid "could not send data to WAL stream: %s" msgstr "не вдалося передати дані потоку WAL: %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:876 +#: replication/libpqwalreceiver/libpqwalreceiver.c:880 #, c-format msgid "could not create replication slot \"%s\": %s" msgstr "не вдалося створити слот реплікації \"%s\": %s" -#: replication/libpqwalreceiver/libpqwalreceiver.c:921 +#: replication/libpqwalreceiver/libpqwalreceiver.c:925 #, c-format msgid "invalid query response" msgstr "неприпустима відповідь на запит" -#: replication/libpqwalreceiver/libpqwalreceiver.c:922 +#: replication/libpqwalreceiver/libpqwalreceiver.c:926 #, c-format msgid "Expected %d fields, got %d fields." msgstr "Очікувалося %d полів, отримано %d полі." -#: replication/libpqwalreceiver/libpqwalreceiver.c:991 +#: replication/libpqwalreceiver/libpqwalreceiver.c:995 #, c-format msgid "the query interface requires a database connection" msgstr "інтерфейс запитів вимагає підключення до бази даних" -#: replication/libpqwalreceiver/libpqwalreceiver.c:1022 +#: replication/libpqwalreceiver/libpqwalreceiver.c:1026 msgid "empty query" msgstr "пустий запит" @@ -18424,12 +18423,12 @@ msgid "could not read from file \"%s\": read %d instead of %d bytes" msgstr "не вдалося прочитати з файлу \"%s\": прочитано %d замість %d байт" -#: replication/logical/snapbuild.c:643 +#: replication/logical/snapbuild.c:655 #, c-format msgid "initial slot snapshot too large" msgstr "початковий знімок слота занадто великий" -#: replication/logical/snapbuild.c:697 +#: replication/logical/snapbuild.c:709 #, c-format msgid "exported logical decoding snapshot: \"%s\" with %u transaction ID" msgid_plural "exported logical decoding snapshot: \"%s\" with %u transaction IDs" @@ -18438,58 +18437,58 @@ msgstr[2] "експортовано знімок логічного декодування \"%s\" з %u ID транзакціями" msgstr[3] "експортовано знімок логічного декодування \"%s\" з %u ID транзакціями" -#: replication/logical/snapbuild.c:1369 replication/logical/snapbuild.c:1476 -#: replication/logical/snapbuild.c:2033 +#: replication/logical/snapbuild.c:1381 replication/logical/snapbuild.c:1488 +#: replication/logical/snapbuild.c:2045 #, c-format msgid "logical decoding found consistent point at %X/%X" msgstr "узгодження процесу логічного кодування знайдено в точці %X/%X" -#: replication/logical/snapbuild.c:1371 +#: replication/logical/snapbuild.c:1383 #, c-format msgid "There are no running transactions." msgstr "Більше активних транзакцій немає." -#: replication/logical/snapbuild.c:1427 +#: replication/logical/snapbuild.c:1439 #, c-format msgid "logical decoding found initial starting point at %X/%X" msgstr "початкова стартова точка процесу логічного декодування знайдена в точці %X/%X" -#: replication/logical/snapbuild.c:1429 replication/logical/snapbuild.c:1453 +#: replication/logical/snapbuild.c:1441 replication/logical/snapbuild.c:1465 #, c-format msgid "Waiting for transactions (approximately %d) older than %u to end." msgstr "Очікування транзакцій (приблизно %d) старіше, ніж %u до кінця." -#: replication/logical/snapbuild.c:1451 +#: replication/logical/snapbuild.c:1463 #, c-format msgid "logical decoding found initial consistent point at %X/%X" msgstr "початкова точка узгодження процесу логічного кодування знайдена в точці %X/%X" -#: replication/logical/snapbuild.c:1478 +#: replication/logical/snapbuild.c:1490 #, c-format msgid "There are no old transactions anymore." msgstr "Більше старих транзакцій немає." -#: replication/logical/snapbuild.c:1875 +#: replication/logical/snapbuild.c:1887 #, c-format msgid "snapbuild state file \"%s\" has wrong magic number: %u instead of %u" msgstr "файл стану snapbuild \"%s\" має неправильне магічне число: %u замість %u" -#: replication/logical/snapbuild.c:1881 +#: replication/logical/snapbuild.c:1893 #, c-format msgid "snapbuild state file \"%s\" has unsupported version: %u instead of %u" msgstr "файл стану snapbuild \"%s\" має непідтримуючу версію: %u замість %u" -#: replication/logical/snapbuild.c:1980 +#: replication/logical/snapbuild.c:1992 #, c-format msgid "checksum mismatch for snapbuild state file \"%s\": is %u, should be %u" msgstr "у файлі стану snapbuild \"%s\" невідповідність контрольної суми: %u, повинно бути %u" -#: replication/logical/snapbuild.c:2035 +#: replication/logical/snapbuild.c:2047 #, c-format msgid "Logical decoding will begin using saved snapshot." msgstr "Логічне декодування почнеться зі збереженого знімку." -#: replication/logical/snapbuild.c:2107 +#: replication/logical/snapbuild.c:2119 #, c-format msgid "could not parse file name \"%s\"" msgstr "не вдалося аналізувати ім'я файлу \"%s\"" @@ -18499,32 +18498,32 @@ msgid "logical replication table synchronization worker for subscription \"%s\", table \"%s\" has finished" msgstr "процес синхронізації таблиці при логічній реплікації для підписки \"%s\", таблиці \"%s\" закінчив обробку" -#: replication/logical/tablesync.c:665 +#: replication/logical/tablesync.c:675 #, c-format msgid "could not fetch table info for table \"%s.%s\" from publisher: %s" msgstr "не вдалося отримати інформацію про таблицю \"%s.%s\" з серверу публікації: %s" -#: replication/logical/tablesync.c:671 +#: replication/logical/tablesync.c:681 #, c-format msgid "table \"%s.%s\" not found on publisher" msgstr "таблиця \"%s.%s\" не знайдена на сервері публікації" -#: replication/logical/tablesync.c:707 +#: replication/logical/tablesync.c:717 #, c-format msgid "could not fetch table info for table \"%s.%s\": %s" msgstr "не вдалося отримати інформацію про таблицю \"%s.%s\": %s" -#: replication/logical/tablesync.c:794 +#: replication/logical/tablesync.c:804 #, c-format msgid "could not start initial contents copy for table \"%s.%s\": %s" msgstr "не вдалося почати копіювання початкового змісту таблиці \"%s.%s\": %s" -#: replication/logical/tablesync.c:909 +#: replication/logical/tablesync.c:919 #, c-format msgid "table copy could not start transaction on publisher" msgstr "під час копіювання таблиці не вдалося почати транзакцію на сервері публікації" -#: replication/logical/tablesync.c:931 +#: replication/logical/tablesync.c:941 #, c-format msgid "table copy could not finish transaction on publisher" msgstr "під час копіювання таблиці не вдалося завершити транзакцію на сервері публікації" @@ -19770,17 +19769,17 @@ msgid "%s failed: %m" msgstr "%s помилка: %m" -#: storage/ipc/procarray.c:3127 +#: storage/ipc/procarray.c:3126 #, c-format msgid "database \"%s\" is being used by prepared transactions" msgstr "база даних \"%s\" використовується підготовленими транзакціями" -#: storage/ipc/procarray.c:3159 storage/ipc/signalfuncs.c:142 +#: storage/ipc/procarray.c:3158 storage/ipc/signalfuncs.c:147 #, c-format msgid "must be a superuser to terminate superuser process" msgstr "щоб припинити процес суперкористувача потрібно бути суперкористувачем" -#: storage/ipc/procarray.c:3166 storage/ipc/signalfuncs.c:147 +#: storage/ipc/procarray.c:3165 storage/ipc/signalfuncs.c:152 #, 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" @@ -19835,33 +19834,33 @@ msgid "PID %d is not a PostgreSQL server process" msgstr "PID %d не є серверним процесом PostgreSQL" -#: storage/ipc/signalfuncs.c:98 storage/lmgr/proc.c:1372 +#: storage/ipc/signalfuncs.c:103 storage/lmgr/proc.c:1380 #, c-format msgid "could not send signal to process %d: %m" msgstr "не вдалося надіслати сигнал процесу %d: %m" -#: storage/ipc/signalfuncs.c:118 +#: storage/ipc/signalfuncs.c:123 #, c-format msgid "must be a superuser to cancel superuser query" msgstr "щоб скасувати запит суперкористувача потрібно бути суперкористувачем" -#: storage/ipc/signalfuncs.c:123 +#: storage/ipc/signalfuncs.c:128 #, c-format msgid "must be a member of the role whose query is being canceled or member of pg_signal_backend" msgstr "потрібно бути учасником ролі, запит котрої скасовується, або учасником pg_signal_backend" -#: storage/ipc/signalfuncs.c:183 +#: storage/ipc/signalfuncs.c:188 #, c-format msgid "must be superuser to rotate log files with adminpack 1.0" msgstr "прокручувати файли протоколів використовуючи adminpack 1.0, може лише суперкористувач" #. translator: %s is a SQL function name -#: storage/ipc/signalfuncs.c:185 utils/adt/genfile.c:253 +#: storage/ipc/signalfuncs.c:190 utils/adt/genfile.c:253 #, c-format msgid "Consider using %s, which is part of core, instead." msgstr "Розгляньте використання %s, що є частиною ядра." -#: storage/ipc/signalfuncs.c:191 storage/ipc/signalfuncs.c:211 +#: storage/ipc/signalfuncs.c:196 storage/ipc/signalfuncs.c:216 #, c-format msgid "rotation not possible because log collection not active" msgstr "обертання неможливе тому, що записування колекції не активоване" @@ -20112,37 +20111,37 @@ msgid "number of requested standby connections exceeds max_wal_senders (currently %d)" msgstr "кількість запитаних підключень резервного серверу перевищує max_wal_senders (поточна %d)" -#: storage/lmgr/proc.c:1343 +#: storage/lmgr/proc.c:1351 #, c-format msgid "Process %d waits for %s on %s." msgstr "Процес %d очікує в режимі %s блокування %s." -#: storage/lmgr/proc.c:1354 +#: storage/lmgr/proc.c:1362 #, c-format msgid "sending cancel to blocking autovacuum PID %d" msgstr "зняття блокуючого процесу автоочистки PID %d" -#: storage/lmgr/proc.c:1474 +#: storage/lmgr/proc.c:1482 #, c-format msgid "process %d avoided deadlock for %s on %s by rearranging queue order after %ld.%03d ms" msgstr "процес %d уникнув взаємного блокування, чекаючи в режимі %s блокування %s змінивши порядок черги після %ld.%03d мс" -#: storage/lmgr/proc.c:1489 +#: storage/lmgr/proc.c:1497 #, c-format msgid "process %d detected deadlock while waiting for %s on %s after %ld.%03d ms" msgstr "процес %d виявив взаємне блокування, чекаючи в режимі %s блокування %s після %ld.%03d мс" -#: storage/lmgr/proc.c:1498 +#: storage/lmgr/proc.c:1506 #, 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:1505 +#: storage/lmgr/proc.c:1513 #, c-format msgid "process %d acquired %s on %s after %ld.%03d ms" msgstr "процес %d отримав в режимі %s блокування %s після %ld.%03d мс" -#: storage/lmgr/proc.c:1521 +#: storage/lmgr/proc.c:1529 #, c-format msgid "process %d failed to acquire %s on %s after %ld.%03d ms" msgstr "процес %d не зміг отримати в режимі %s блокування %s після %ld.%03d мс" @@ -21055,133 +21054,133 @@ msgid "initial position must not be null" msgstr "початкова позиція не повинна бути null" -#: utils/adt/arrayfuncs.c:270 utils/adt/arrayfuncs.c:284 -#: utils/adt/arrayfuncs.c:295 utils/adt/arrayfuncs.c:317 -#: utils/adt/arrayfuncs.c:332 utils/adt/arrayfuncs.c:346 -#: utils/adt/arrayfuncs.c:352 utils/adt/arrayfuncs.c:359 -#: utils/adt/arrayfuncs.c:492 utils/adt/arrayfuncs.c:508 -#: utils/adt/arrayfuncs.c:519 utils/adt/arrayfuncs.c:534 -#: utils/adt/arrayfuncs.c:555 utils/adt/arrayfuncs.c:585 -#: utils/adt/arrayfuncs.c:592 utils/adt/arrayfuncs.c:600 -#: utils/adt/arrayfuncs.c:634 utils/adt/arrayfuncs.c:657 -#: utils/adt/arrayfuncs.c:677 utils/adt/arrayfuncs.c:789 -#: utils/adt/arrayfuncs.c:798 utils/adt/arrayfuncs.c:828 -#: utils/adt/arrayfuncs.c:843 utils/adt/arrayfuncs.c:896 +#: utils/adt/arrayfuncs.c:271 utils/adt/arrayfuncs.c:285 +#: utils/adt/arrayfuncs.c:296 utils/adt/arrayfuncs.c:318 +#: utils/adt/arrayfuncs.c:333 utils/adt/arrayfuncs.c:347 +#: utils/adt/arrayfuncs.c:353 utils/adt/arrayfuncs.c:360 +#: utils/adt/arrayfuncs.c:493 utils/adt/arrayfuncs.c:509 +#: utils/adt/arrayfuncs.c:520 utils/adt/arrayfuncs.c:535 +#: utils/adt/arrayfuncs.c:556 utils/adt/arrayfuncs.c:586 +#: utils/adt/arrayfuncs.c:593 utils/adt/arrayfuncs.c:601 +#: utils/adt/arrayfuncs.c:635 utils/adt/arrayfuncs.c:658 +#: utils/adt/arrayfuncs.c:678 utils/adt/arrayfuncs.c:790 +#: utils/adt/arrayfuncs.c:799 utils/adt/arrayfuncs.c:829 +#: utils/adt/arrayfuncs.c:844 utils/adt/arrayfuncs.c:897 #, c-format msgid "malformed array literal: \"%s\"" msgstr "неправильний літерал масиву: \"%s\"" -#: utils/adt/arrayfuncs.c:271 +#: utils/adt/arrayfuncs.c:272 #, c-format msgid "\"[\" must introduce explicitly-specified array dimensions." msgstr "\"[\" повинно представляти явно вказані виміри масиву." -#: utils/adt/arrayfuncs.c:285 +#: utils/adt/arrayfuncs.c:286 #, c-format msgid "Missing array dimension value." msgstr "Пропущено значення виміру масиву." -#: utils/adt/arrayfuncs.c:296 utils/adt/arrayfuncs.c:333 +#: utils/adt/arrayfuncs.c:297 utils/adt/arrayfuncs.c:334 #, c-format msgid "Missing \"%s\" after array dimensions." msgstr "Пропущено \"%s\" після вимірів масиву." -#: utils/adt/arrayfuncs.c:305 utils/adt/arrayfuncs.c:2882 -#: utils/adt/arrayfuncs.c:2914 utils/adt/arrayfuncs.c:2929 +#: utils/adt/arrayfuncs.c:306 utils/adt/arrayfuncs.c:2918 +#: utils/adt/arrayfuncs.c:2963 utils/adt/arrayfuncs.c:2978 #, c-format msgid "upper bound cannot be less than lower bound" msgstr "верхня границя не може бути меньше нижньої границі" -#: utils/adt/arrayfuncs.c:318 +#: utils/adt/arrayfuncs.c:319 #, c-format msgid "Array value must start with \"{\" or dimension information." msgstr "Значення масиву повинно починатись з \"{\" або з інформації про вимір." -#: utils/adt/arrayfuncs.c:347 +#: utils/adt/arrayfuncs.c:348 #, c-format msgid "Array contents must start with \"{\"." msgstr "Вміст масиву повинен починатись з \"{\"." -#: utils/adt/arrayfuncs.c:353 utils/adt/arrayfuncs.c:360 +#: utils/adt/arrayfuncs.c:354 utils/adt/arrayfuncs.c:361 #, c-format msgid "Specified array dimensions do not match array contents." msgstr "Вказані виміри масиву не відповідають його вмісту." -#: utils/adt/arrayfuncs.c:493 utils/adt/arrayfuncs.c:520 +#: utils/adt/arrayfuncs.c:494 utils/adt/arrayfuncs.c:521 #: utils/adt/rangetypes.c:2181 utils/adt/rangetypes.c:2189 #: utils/adt/rowtypes.c:210 utils/adt/rowtypes.c:218 #, c-format msgid "Unexpected end of input." msgstr "Неочікуваний кінец введення." -#: utils/adt/arrayfuncs.c:509 utils/adt/arrayfuncs.c:556 -#: utils/adt/arrayfuncs.c:586 utils/adt/arrayfuncs.c:635 +#: utils/adt/arrayfuncs.c:510 utils/adt/arrayfuncs.c:557 +#: utils/adt/arrayfuncs.c:587 utils/adt/arrayfuncs.c:636 #, c-format msgid "Unexpected \"%c\" character." msgstr "Неочікуваний символ \"%c\"." -#: utils/adt/arrayfuncs.c:535 utils/adt/arrayfuncs.c:658 +#: utils/adt/arrayfuncs.c:536 utils/adt/arrayfuncs.c:659 #, c-format msgid "Unexpected array element." msgstr "Неочікуваний елемент масиву." -#: utils/adt/arrayfuncs.c:593 +#: utils/adt/arrayfuncs.c:594 #, c-format msgid "Unmatched \"%c\" character." msgstr "Невідповідний символ \"%c\"." -#: utils/adt/arrayfuncs.c:601 utils/adt/jsonfuncs.c:2452 +#: utils/adt/arrayfuncs.c:602 utils/adt/jsonfuncs.c:2452 #, c-format msgid "Multidimensional arrays must have sub-arrays with matching dimensions." msgstr "Багатовимірні масиви повинні мати вкладені масиви з відповідними вимірами." -#: utils/adt/arrayfuncs.c:678 +#: utils/adt/arrayfuncs.c:679 #, c-format msgid "Junk after closing right brace." msgstr "Сміття після закриття правої дужки." -#: utils/adt/arrayfuncs.c:1300 utils/adt/arrayfuncs.c:3342 -#: utils/adt/arrayfuncs.c:5821 +#: utils/adt/arrayfuncs.c:1301 utils/adt/arrayfuncs.c:3391 +#: utils/adt/arrayfuncs.c:5870 #, c-format msgid "invalid number of dimensions: %d" msgstr "неприпустима кількість вимірів: %d" -#: utils/adt/arrayfuncs.c:1311 +#: utils/adt/arrayfuncs.c:1312 #, c-format msgid "invalid array flags" msgstr "неприпустимі позначки масиву" -#: utils/adt/arrayfuncs.c:1319 +#: utils/adt/arrayfuncs.c:1320 #, c-format msgid "wrong element type" msgstr "неправильний тип елементу" -#: utils/adt/arrayfuncs.c:1356 utils/adt/rangetypes.c:335 +#: utils/adt/arrayfuncs.c:1357 utils/adt/rangetypes.c:335 #: utils/cache/lsyscache.c:2862 #, c-format msgid "no binary input function available for type %s" msgstr "для типу %s немає функції введення двійкових даних" -#: utils/adt/arrayfuncs.c:1496 +#: utils/adt/arrayfuncs.c:1497 #, c-format msgid "improper binary format in array element %d" msgstr "неправильний двійковий формат в елементі масиву %d" -#: utils/adt/arrayfuncs.c:1577 utils/adt/rangetypes.c:340 +#: utils/adt/arrayfuncs.c:1578 utils/adt/rangetypes.c:340 #: utils/cache/lsyscache.c:2895 #, c-format msgid "no binary output function available for type %s" msgstr "для типу %s немає функції виводу двійкових даних" -#: utils/adt/arrayfuncs.c:2055 +#: utils/adt/arrayfuncs.c:2056 #, c-format msgid "slices of fixed-length arrays not implemented" msgstr "розрізання масивів постійної довжини не реалізовано" -#: utils/adt/arrayfuncs.c:2233 utils/adt/arrayfuncs.c:2255 -#: utils/adt/arrayfuncs.c:2304 utils/adt/arrayfuncs.c:2542 -#: utils/adt/arrayfuncs.c:2860 utils/adt/arrayfuncs.c:5807 -#: utils/adt/arrayfuncs.c:5833 utils/adt/arrayfuncs.c:5844 +#: utils/adt/arrayfuncs.c:2234 utils/adt/arrayfuncs.c:2256 +#: utils/adt/arrayfuncs.c:2305 utils/adt/arrayfuncs.c:2559 +#: utils/adt/arrayfuncs.c:2893 utils/adt/arrayfuncs.c:5856 +#: utils/adt/arrayfuncs.c:5882 utils/adt/arrayfuncs.c:5893 #: utils/adt/json.c:1141 utils/adt/json.c:1216 utils/adt/jsonb.c:1316 #: utils/adt/jsonb.c:1402 utils/adt/jsonfuncs.c:4340 utils/adt/jsonfuncs.c:4490 #: utils/adt/jsonfuncs.c:4602 utils/adt/jsonfuncs.c:4648 @@ -21189,130 +21188,130 @@ msgid "wrong number of array subscripts" msgstr "невірне число верхніх індексів масива" -#: utils/adt/arrayfuncs.c:2238 utils/adt/arrayfuncs.c:2346 -#: utils/adt/arrayfuncs.c:2606 utils/adt/arrayfuncs.c:2919 +#: utils/adt/arrayfuncs.c:2239 utils/adt/arrayfuncs.c:2363 +#: utils/adt/arrayfuncs.c:2639 utils/adt/arrayfuncs.c:2968 #, c-format msgid "array subscript out of range" msgstr "верхній індекс масиву поза діапазоном" -#: utils/adt/arrayfuncs.c:2243 +#: utils/adt/arrayfuncs.c:2244 #, c-format msgid "cannot assign null value to an element of a fixed-length array" msgstr "не можна призначати значення null значення елементу масива постійної довжини" -#: utils/adt/arrayfuncs.c:2807 +#: utils/adt/arrayfuncs.c:2840 #, c-format msgid "updates on slices of fixed-length arrays not implemented" msgstr "оновлення в зрізах масивів постійної довжини не реалізовані" -#: utils/adt/arrayfuncs.c:2838 +#: utils/adt/arrayfuncs.c:2871 #, c-format msgid "array slice subscript must provide both boundaries" msgstr "у вказівці зрізу масива повинні бути задані обидві межі" -#: utils/adt/arrayfuncs.c:2839 +#: utils/adt/arrayfuncs.c:2872 #, c-format msgid "When assigning to a slice of an empty array value, slice boundaries must be fully specified." msgstr "Під час присвоєння значень зрізу в пустому масиві, межі зрізу повинні вказуватися повністю." -#: utils/adt/arrayfuncs.c:2850 utils/adt/arrayfuncs.c:2946 +#: utils/adt/arrayfuncs.c:2883 utils/adt/arrayfuncs.c:2995 #, c-format msgid "source array too small" msgstr "вихідний масив занадто малий" -#: utils/adt/arrayfuncs.c:3500 +#: utils/adt/arrayfuncs.c:3549 #, c-format msgid "null array element not allowed in this context" msgstr "елемент масиву null не дозволений в цьому контексті" -#: utils/adt/arrayfuncs.c:3602 utils/adt/arrayfuncs.c:3773 -#: utils/adt/arrayfuncs.c:4129 +#: utils/adt/arrayfuncs.c:3651 utils/adt/arrayfuncs.c:3822 +#: utils/adt/arrayfuncs.c:4178 #, c-format msgid "cannot compare arrays of different element types" msgstr "не можна порівнювати масиви з елементами різних типів" -#: utils/adt/arrayfuncs.c:3951 utils/adt/rangetypes.c:1254 +#: utils/adt/arrayfuncs.c:4000 utils/adt/rangetypes.c:1254 #: utils/adt/rangetypes.c:1318 #, c-format msgid "could not identify a hash function for type %s" msgstr "не вдалося визначити геш-функцію для типу %s" -#: utils/adt/arrayfuncs.c:4044 +#: utils/adt/arrayfuncs.c:4093 #, c-format msgid "could not identify an extended hash function for type %s" msgstr "не вдалося визначити розширену геш-функцію для типу %s" -#: utils/adt/arrayfuncs.c:5221 +#: utils/adt/arrayfuncs.c:5270 #, c-format msgid "data type %s is not an array type" msgstr "тип даних %s не є типом масиву" -#: utils/adt/arrayfuncs.c:5276 +#: utils/adt/arrayfuncs.c:5325 #, c-format msgid "cannot accumulate null arrays" msgstr "накопичувати null-масиви не можна" -#: utils/adt/arrayfuncs.c:5304 +#: utils/adt/arrayfuncs.c:5353 #, c-format msgid "cannot accumulate empty arrays" msgstr "накопичувати пусті масиви не можна" -#: utils/adt/arrayfuncs.c:5331 utils/adt/arrayfuncs.c:5337 +#: utils/adt/arrayfuncs.c:5380 utils/adt/arrayfuncs.c:5386 #, c-format msgid "cannot accumulate arrays of different dimensionality" msgstr "накопичувати масиви різної розмірності не можна" -#: utils/adt/arrayfuncs.c:5705 utils/adt/arrayfuncs.c:5745 +#: utils/adt/arrayfuncs.c:5754 utils/adt/arrayfuncs.c:5794 #, c-format msgid "dimension array or low bound array cannot be null" msgstr "масив розмірності або масив нижніх границь не може бути null" -#: utils/adt/arrayfuncs.c:5808 utils/adt/arrayfuncs.c:5834 +#: utils/adt/arrayfuncs.c:5857 utils/adt/arrayfuncs.c:5883 #, c-format msgid "Dimension array must be one dimensional." msgstr "Масив розмірності повинен бути одновимірним." -#: utils/adt/arrayfuncs.c:5813 utils/adt/arrayfuncs.c:5839 +#: utils/adt/arrayfuncs.c:5862 utils/adt/arrayfuncs.c:5888 #, c-format msgid "dimension values cannot be null" msgstr "значення розмірностей не можуть бути null" -#: utils/adt/arrayfuncs.c:5845 +#: utils/adt/arrayfuncs.c:5894 #, c-format msgid "Low bound array has different size than dimensions array." msgstr "Масив нижніх границь відрізняється за розміром від масиву розмірностей." -#: utils/adt/arrayfuncs.c:6123 +#: utils/adt/arrayfuncs.c:6172 #, c-format msgid "removing elements from multidimensional arrays is not supported" msgstr "видалення елементів з багатовимірних масивів не підтримується" -#: utils/adt/arrayfuncs.c:6400 +#: utils/adt/arrayfuncs.c:6449 #, c-format msgid "thresholds must be one-dimensional array" msgstr "граничне значення повинно вказуватись одновимірним масивом" -#: utils/adt/arrayfuncs.c:6405 +#: utils/adt/arrayfuncs.c:6454 #, c-format msgid "thresholds array must not contain NULLs" msgstr "масив границь не повинен містити NULL" -#: utils/adt/arrayutils.c:140 +#: utils/adt/arrayutils.c:134 #, c-format msgid "array lower bound is too large: %d" msgstr "нижня границя масиву занадто велика: %d" -#: utils/adt/arrayutils.c:240 +#: utils/adt/arrayutils.c:234 #, c-format msgid "typmod array must be type cstring[]" msgstr "масив typmod повинен мати тип cstring[]" -#: utils/adt/arrayutils.c:245 +#: utils/adt/arrayutils.c:239 #, c-format msgid "typmod array must be one-dimensional" msgstr "масив typmod повинен бути одновимірним" -#: utils/adt/arrayutils.c:250 +#: utils/adt/arrayutils.c:244 #, c-format msgid "typmod array must not contain nulls" msgstr "масив typmod не повинен містити елементи nulls" @@ -21340,7 +21339,7 @@ #: utils/adt/numutils.c:246 utils/adt/numutils.c:322 utils/adt/oid.c:44 #: utils/adt/oid.c:58 utils/adt/oid.c:64 utils/adt/oid.c:86 #: utils/adt/pg_lsn.c:73 utils/adt/tid.c:74 utils/adt/tid.c:82 -#: utils/adt/tid.c:90 utils/adt/timestamp.c:494 utils/adt/uuid.c:136 +#: utils/adt/tid.c:90 utils/adt/timestamp.c:495 utils/adt/uuid.c:136 #: utils/adt/xid8funcs.c:347 #, c-format msgid "invalid input syntax for type %s: \"%s\"" @@ -21361,7 +21360,7 @@ #: utils/adt/int.c:1148 utils/adt/int8.c:593 utils/adt/int8.c:651 #: utils/adt/int8.c:978 utils/adt/int8.c:1058 utils/adt/int8.c:1120 #: utils/adt/int8.c:1200 utils/adt/numeric.c:7431 utils/adt/numeric.c:7721 -#: utils/adt/numeric.c:9366 utils/adt/timestamp.c:3275 +#: utils/adt/numeric.c:9366 utils/adt/timestamp.c:3281 #, c-format msgid "division by zero" msgstr "ділення на нуль" @@ -21371,7 +21370,7 @@ msgid "\"char\" out of range" msgstr "значення \"char\" поза діапазоном" -#: utils/adt/date.c:61 utils/adt/timestamp.c:95 utils/adt/varbit.c:104 +#: utils/adt/date.c:61 utils/adt/timestamp.c:96 utils/adt/varbit.c:104 #: utils/adt/varchar.c:48 #, c-format msgid "invalid type modifier" @@ -21400,12 +21399,12 @@ msgid "date out of range" msgstr "дата поза діапазоном" -#: utils/adt/date.c:259 utils/adt/timestamp.c:574 +#: utils/adt/date.c:259 utils/adt/timestamp.c:575 #, c-format msgid "date field value out of range: %d-%02d-%02d" msgstr "значення поля типу date поза діапазоном: %d-%02d-%02d" -#: utils/adt/date.c:266 utils/adt/date.c:275 utils/adt/timestamp.c:580 +#: utils/adt/date.c:266 utils/adt/date.c:275 utils/adt/timestamp.c:581 #, c-format msgid "date out of range: %d-%02d-%02d" msgstr "дата поза діапазоном: %d-%02d-%02d" @@ -21416,24 +21415,24 @@ #: utils/adt/datetime.c:1655 utils/adt/formatting.c:4110 #: utils/adt/formatting.c:4142 utils/adt/formatting.c:4222 #: utils/adt/formatting.c:4344 utils/adt/json.c:418 utils/adt/json.c:457 -#: utils/adt/timestamp.c:222 utils/adt/timestamp.c:254 -#: utils/adt/timestamp.c:692 utils/adt/timestamp.c:701 -#: utils/adt/timestamp.c:779 utils/adt/timestamp.c:812 -#: utils/adt/timestamp.c:2854 utils/adt/timestamp.c:2875 -#: utils/adt/timestamp.c:2888 utils/adt/timestamp.c:2897 -#: utils/adt/timestamp.c:2905 utils/adt/timestamp.c:2960 -#: utils/adt/timestamp.c:2983 utils/adt/timestamp.c:2996 -#: utils/adt/timestamp.c:3007 utils/adt/timestamp.c:3015 -#: utils/adt/timestamp.c:3675 utils/adt/timestamp.c:3800 -#: utils/adt/timestamp.c:3841 utils/adt/timestamp.c:3931 -#: utils/adt/timestamp.c:3975 utils/adt/timestamp.c:4078 -#: utils/adt/timestamp.c:4563 utils/adt/timestamp.c:4759 -#: utils/adt/timestamp.c:5086 utils/adt/timestamp.c:5100 -#: utils/adt/timestamp.c:5105 utils/adt/timestamp.c:5119 -#: utils/adt/timestamp.c:5152 utils/adt/timestamp.c:5239 -#: utils/adt/timestamp.c:5280 utils/adt/timestamp.c:5284 -#: utils/adt/timestamp.c:5353 utils/adt/timestamp.c:5357 -#: utils/adt/timestamp.c:5371 utils/adt/timestamp.c:5405 utils/adt/xml.c:2232 +#: utils/adt/timestamp.c:223 utils/adt/timestamp.c:255 +#: utils/adt/timestamp.c:693 utils/adt/timestamp.c:702 +#: utils/adt/timestamp.c:780 utils/adt/timestamp.c:813 +#: utils/adt/timestamp.c:2855 utils/adt/timestamp.c:2876 +#: utils/adt/timestamp.c:2889 utils/adt/timestamp.c:2898 +#: utils/adt/timestamp.c:2906 utils/adt/timestamp.c:2961 +#: utils/adt/timestamp.c:2984 utils/adt/timestamp.c:2997 +#: utils/adt/timestamp.c:3008 utils/adt/timestamp.c:3016 +#: utils/adt/timestamp.c:3703 utils/adt/timestamp.c:3828 +#: utils/adt/timestamp.c:3869 utils/adt/timestamp.c:3959 +#: utils/adt/timestamp.c:4003 utils/adt/timestamp.c:4106 +#: utils/adt/timestamp.c:4591 utils/adt/timestamp.c:4787 +#: utils/adt/timestamp.c:5114 utils/adt/timestamp.c:5128 +#: utils/adt/timestamp.c:5133 utils/adt/timestamp.c:5147 +#: utils/adt/timestamp.c:5180 utils/adt/timestamp.c:5267 +#: utils/adt/timestamp.c:5308 utils/adt/timestamp.c:5312 +#: utils/adt/timestamp.c:5381 utils/adt/timestamp.c:5385 +#: utils/adt/timestamp.c:5399 utils/adt/timestamp.c:5433 utils/adt/xml.c:2232 #: utils/adt/xml.c:2239 utils/adt/xml.c:2259 utils/adt/xml.c:2266 #, c-format msgid "timestamp out of range" @@ -21455,7 +21454,7 @@ msgid "time out of range" msgstr "час поза діапазоном" -#: utils/adt/date.c:1413 utils/adt/timestamp.c:589 +#: utils/adt/date.c:1413 utils/adt/timestamp.c:590 #, c-format msgid "time field value out of range: %d:%02d:%02g" msgstr "значення поля типу time поза діапазоном: %d:%02d:%02g" @@ -21463,8 +21462,8 @@ #: utils/adt/date.c:1933 utils/adt/date.c:2435 utils/adt/float.c:1071 #: utils/adt/float.c:1140 utils/adt/int.c:616 utils/adt/int.c:663 #: utils/adt/int.c:698 utils/adt/int8.c:492 utils/adt/numeric.c:2189 -#: utils/adt/timestamp.c:3324 utils/adt/timestamp.c:3355 -#: utils/adt/timestamp.c:3386 +#: utils/adt/timestamp.c:3352 utils/adt/timestamp.c:3383 +#: utils/adt/timestamp.c:3414 #, c-format msgid "invalid preceding or following size in window function" msgstr "неприпустимий розмір preceding або following у віконній функції" @@ -21485,14 +21484,14 @@ msgstr "\"час з часовим поясом\" містить нерозпізнані одиниці \"%s\"" #: utils/adt/date.c:2856 utils/adt/datetime.c:906 utils/adt/datetime.c:1813 -#: utils/adt/datetime.c:4601 utils/adt/timestamp.c:513 -#: utils/adt/timestamp.c:540 utils/adt/timestamp.c:4161 -#: utils/adt/timestamp.c:5111 utils/adt/timestamp.c:5363 +#: utils/adt/datetime.c:4601 utils/adt/timestamp.c:514 +#: utils/adt/timestamp.c:541 utils/adt/timestamp.c:4189 +#: utils/adt/timestamp.c:5139 utils/adt/timestamp.c:5391 #, c-format msgid "time zone \"%s\" not recognized" msgstr "часовий пояс \"%s\" не розпізнаний" -#: utils/adt/date.c:2888 utils/adt/timestamp.c:5141 utils/adt/timestamp.c:5394 +#: utils/adt/date.c:2889 utils/adt/timestamp.c:5169 utils/adt/timestamp.c:5422 #, c-format msgid "interval time zone \"%s\" must not include months or days" msgstr "інтервал \"%s\", який задає часовий пояс, не повинен включати місяці або дні" @@ -21522,7 +21521,7 @@ msgid "This time zone name appears in the configuration file for time zone abbreviation \"%s\"." msgstr "Це ім'я часового поясу з'являється у файлі конфігурації часового поясу з кодом \"%s\"." -#: utils/adt/datum.c:89 utils/adt/datum.c:101 +#: utils/adt/datum.c:90 utils/adt/datum.c:102 #, c-format msgid "invalid Datum pointer" msgstr "неприпустимий вказівник Datum" @@ -22110,7 +22109,7 @@ msgstr "oidvector має занадто багато елементів" #: utils/adt/int.c:1510 utils/adt/int8.c:1439 utils/adt/numeric.c:1409 -#: utils/adt/timestamp.c:5456 utils/adt/timestamp.c:5536 +#: utils/adt/timestamp.c:5484 utils/adt/timestamp.c:5564 #, c-format msgid "step size cannot equal zero" msgstr "розмір кроку не може дорівнювати нулю" @@ -22140,7 +22139,7 @@ msgid "key value must be scalar, not array, composite, or json" msgstr "значенням ключа повинен бути скаляр, не масив, композитний тип, або json" -#: utils/adt/json.c:892 utils/adt/json.c:902 utils/fmgr/funcapi.c:1813 +#: utils/adt/json.c:892 utils/adt/json.c:902 utils/fmgr/funcapi.c:1847 #, c-format msgid "could not determine data type for argument %d" msgstr "не вдалося визначити тип даних для аргументу %d" @@ -23153,7 +23152,7 @@ msgstr "Щоб позначити пропущений аргумент унарного оператору, використайте NONE." #: utils/adt/regproc.c:697 utils/adt/regproc.c:738 utils/adt/regproc.c:2018 -#: utils/adt/ruleutils.c:9378 utils/adt/ruleutils.c:9547 +#: utils/adt/ruleutils.c:9386 utils/adt/ruleutils.c:9555 #, c-format msgid "too many arguments" msgstr "занадто багато аргументів" @@ -23334,125 +23333,125 @@ msgid "rule \"%s\" has unsupported event type %d" msgstr "правило \"%s\" має непідтримуваний тип подій %d" -#: utils/adt/timestamp.c:107 +#: utils/adt/timestamp.c:108 #, c-format msgid "TIMESTAMP(%d)%s precision must not be negative" msgstr "TIMESTAMP(%d)%s точність не повинна бути від'ємною" -#: utils/adt/timestamp.c:113 +#: utils/adt/timestamp.c:114 #, c-format msgid "TIMESTAMP(%d)%s precision reduced to maximum allowed, %d" msgstr "TIMESTAMP(%d)%s точність зменшена до дозволеного максимуму, %d" -#: utils/adt/timestamp.c:176 utils/adt/timestamp.c:434 utils/misc/guc.c:11975 +#: utils/adt/timestamp.c:177 utils/adt/timestamp.c:435 utils/misc/guc.c:11983 #, c-format msgid "timestamp out of range: \"%s\"" msgstr "позначка часу поза діапазоном: \"%s\"" -#: utils/adt/timestamp.c:372 +#: utils/adt/timestamp.c:373 #, c-format msgid "timestamp(%d) precision must be between %d and %d" msgstr "точність позначки часу (%d) повинна бути між %d і %d" -#: utils/adt/timestamp.c:496 +#: utils/adt/timestamp.c:497 #, c-format msgid "Numeric time zones must have \"-\" or \"+\" as first character." msgstr "Числові часові пояси повинні мати \"-\" або \"+\" в якості першого символу." -#: utils/adt/timestamp.c:509 +#: utils/adt/timestamp.c:510 #, c-format msgid "numeric time zone \"%s\" out of range" msgstr "числовий часовий пояс \"%s\" поза діапазоном" -#: utils/adt/timestamp.c:601 utils/adt/timestamp.c:611 -#: utils/adt/timestamp.c:619 +#: utils/adt/timestamp.c:602 utils/adt/timestamp.c:612 +#: utils/adt/timestamp.c:620 #, c-format msgid "timestamp out of range: %d-%02d-%02d %d:%02d:%02g" msgstr "позначка часу поза діапазоном: %d-%02d-%02d %d:%02d:%02g" -#: utils/adt/timestamp.c:720 +#: utils/adt/timestamp.c:721 #, c-format msgid "timestamp cannot be NaN" msgstr "позначка часу не може бути NaN" -#: utils/adt/timestamp.c:738 utils/adt/timestamp.c:750 +#: utils/adt/timestamp.c:739 utils/adt/timestamp.c:751 #, c-format msgid "timestamp out of range: \"%g\"" msgstr "позначка часу поза діапазоном: \"%g\"" -#: utils/adt/timestamp.c:935 utils/adt/timestamp.c:1509 -#: utils/adt/timestamp.c:1976 utils/adt/timestamp.c:3053 -#: utils/adt/timestamp.c:3058 utils/adt/timestamp.c:3063 -#: utils/adt/timestamp.c:3113 utils/adt/timestamp.c:3120 -#: utils/adt/timestamp.c:3127 utils/adt/timestamp.c:3147 -#: utils/adt/timestamp.c:3154 utils/adt/timestamp.c:3161 -#: utils/adt/timestamp.c:3191 utils/adt/timestamp.c:3199 -#: utils/adt/timestamp.c:3243 utils/adt/timestamp.c:3670 -#: utils/adt/timestamp.c:3795 utils/adt/timestamp.c:4255 +#: utils/adt/timestamp.c:936 utils/adt/timestamp.c:1510 +#: utils/adt/timestamp.c:1977 utils/adt/timestamp.c:3054 +#: utils/adt/timestamp.c:3059 utils/adt/timestamp.c:3064 +#: utils/adt/timestamp.c:3114 utils/adt/timestamp.c:3121 +#: utils/adt/timestamp.c:3128 utils/adt/timestamp.c:3148 +#: utils/adt/timestamp.c:3155 utils/adt/timestamp.c:3162 +#: utils/adt/timestamp.c:3249 utils/adt/timestamp.c:3324 +#: utils/adt/timestamp.c:3698 utils/adt/timestamp.c:3823 +#: utils/adt/timestamp.c:4283 #, c-format msgid "interval out of range" msgstr "інтервал поза діапазоном" -#: utils/adt/timestamp.c:1062 utils/adt/timestamp.c:1095 +#: utils/adt/timestamp.c:1063 utils/adt/timestamp.c:1096 #, c-format msgid "invalid INTERVAL type modifier" msgstr "неприпустимий модифікатор типу INTERVAL" -#: utils/adt/timestamp.c:1078 +#: utils/adt/timestamp.c:1079 #, c-format msgid "INTERVAL(%d) precision must not be negative" msgstr "INTERVAL(%d) точність не повинна бути від'ємною" -#: utils/adt/timestamp.c:1084 +#: utils/adt/timestamp.c:1085 #, c-format msgid "INTERVAL(%d) precision reduced to maximum allowed, %d" msgstr "INTERVAL(%d) точність зменшена до максимально можливої, %d" -#: utils/adt/timestamp.c:1466 +#: utils/adt/timestamp.c:1467 #, c-format msgid "interval(%d) precision must be between %d and %d" msgstr "interval(%d) точність повинна бути між %d і %d" -#: utils/adt/timestamp.c:2654 +#: utils/adt/timestamp.c:2655 #, c-format msgid "cannot subtract infinite timestamps" msgstr "віднімати безкінечні позначки часу не можна" -#: utils/adt/timestamp.c:3923 utils/adt/timestamp.c:4516 -#: utils/adt/timestamp.c:4678 utils/adt/timestamp.c:4699 +#: utils/adt/timestamp.c:3951 utils/adt/timestamp.c:4544 +#: utils/adt/timestamp.c:4706 utils/adt/timestamp.c:4727 #, c-format msgid "timestamp units \"%s\" not supported" msgstr "одиниці позначки часу \"%s\" не підтримуються" -#: utils/adt/timestamp.c:3937 utils/adt/timestamp.c:4470 -#: utils/adt/timestamp.c:4709 +#: utils/adt/timestamp.c:3965 utils/adt/timestamp.c:4498 +#: utils/adt/timestamp.c:4737 #, c-format msgid "timestamp units \"%s\" not recognized" msgstr "одиниці позначки часу \"%s\" не розпізнані" -#: utils/adt/timestamp.c:4067 utils/adt/timestamp.c:4511 -#: utils/adt/timestamp.c:4874 utils/adt/timestamp.c:4896 +#: utils/adt/timestamp.c:4095 utils/adt/timestamp.c:4539 +#: utils/adt/timestamp.c:4902 utils/adt/timestamp.c:4924 #, c-format msgid "timestamp with time zone units \"%s\" not supported" msgstr "одиниці позначки часу з часовим поясом \"%s\" не підтримуються" -#: utils/adt/timestamp.c:4084 utils/adt/timestamp.c:4465 -#: utils/adt/timestamp.c:4905 +#: utils/adt/timestamp.c:4112 utils/adt/timestamp.c:4493 +#: utils/adt/timestamp.c:4933 #, c-format msgid "timestamp with time zone units \"%s\" not recognized" msgstr "одиниці позначки часу з часовим поясом \"%s\" не розпізнані" -#: utils/adt/timestamp.c:4242 +#: utils/adt/timestamp.c:4270 #, c-format msgid "interval units \"%s\" not supported because months usually have fractional weeks" msgstr "одиниці інтервалу \"%s\" не підтримуються, тому, що місяці зазвичай мають дробове число тижнів" -#: utils/adt/timestamp.c:4248 utils/adt/timestamp.c:4999 +#: utils/adt/timestamp.c:4276 utils/adt/timestamp.c:5027 #, c-format msgid "interval units \"%s\" not supported" msgstr "одиниці інтервалу \"%s\" не підтримуються" -#: utils/adt/timestamp.c:4264 utils/adt/timestamp.c:5022 +#: utils/adt/timestamp.c:4292 utils/adt/timestamp.c:5050 #, c-format msgid "interval units \"%s\" not recognized" msgstr "одиниці інтервалу \"%s\" не розпізнані" @@ -23950,47 +23949,52 @@ msgid "invalid query" msgstr "неприпустимий запит" -#: utils/adt/xml.c:4016 +#: utils/adt/xml.c:2768 +#, c-format +msgid "portal \"%s\" does not return tuples" +msgstr "portal \"%s\" не повертає кортежі" + +#: utils/adt/xml.c:4020 #, c-format msgid "invalid array for XML namespace mapping" msgstr "неприпустимий масив з зіставленням простіру імен XML" -#: utils/adt/xml.c:4017 +#: utils/adt/xml.c:4021 #, c-format msgid "The array must be two-dimensional with length of the second axis equal to 2." msgstr "Масив повинен бути двовимірним і містити 2 елемента по другій вісі." -#: utils/adt/xml.c:4041 +#: utils/adt/xml.c:4045 #, c-format msgid "empty XPath expression" msgstr "пустий вираз XPath" -#: utils/adt/xml.c:4093 +#: utils/adt/xml.c:4097 #, c-format msgid "neither namespace name nor URI may be null" msgstr "ні ім'я простіру імен ні URI не можуть бути null" -#: utils/adt/xml.c:4100 +#: utils/adt/xml.c:4104 #, c-format msgid "could not register XML namespace with name \"%s\" and URI \"%s\"" msgstr "не вдалося зареєструвати простір імен XML з ім'ям \"%s\" і URI \"%s\"" -#: utils/adt/xml.c:4451 +#: utils/adt/xml.c:4455 #, c-format msgid "DEFAULT namespace is not supported" msgstr "Простір імен DEFAULT не підтримується" -#: utils/adt/xml.c:4480 +#: utils/adt/xml.c:4484 #, c-format msgid "row path filter must not be empty string" msgstr "шлях фільтруючих рядків не повинен бути пустим" -#: utils/adt/xml.c:4511 +#: utils/adt/xml.c:4515 #, c-format msgid "column path filter must not be empty string" msgstr "шлях фільтруючого стовпця не повинен бути пустим" -#: utils/adt/xml.c:4661 +#: utils/adt/xml.c:4665 #, c-format msgid "more than one value returned by column XPath expression" msgstr "вираз XPath, який відбирає стовпець, повернув більше одного значення" @@ -24021,7 +24025,7 @@ msgid "operator class \"%s\" of access method %s is missing support function %d for type %s" msgstr "в класі операторів \"%s\" методу доступу %s пропущено опорну функцію %d для типу %s" -#: utils/cache/plancache.c:720 +#: utils/cache/plancache.c:722 #, c-format msgid "cached plan must not change result type" msgstr "в кешованому плані не повинен змінюватись тип результату" @@ -24056,7 +24060,7 @@ msgid "relation mapping file \"%s\" contains incorrect checksum" msgstr "файл зіставлень відношень \"%s\" містить неправильну контрольну суму" -#: utils/cache/typcache.c:1692 utils/fmgr/funcapi.c:461 +#: utils/cache/typcache.c:1692 utils/fmgr/funcapi.c:495 #, c-format msgid "record type has not been registered" msgstr "тип запису не зареєстрований" @@ -24275,22 +24279,22 @@ msgid "language validation function %u called for language %u instead of %u" msgstr "функція мовної перевірки %u викликана для мови %u замість %u" -#: utils/fmgr/funcapi.c:384 +#: utils/fmgr/funcapi.c:418 #, c-format msgid "could not determine actual result type for function \"%s\" declared to return type %s" msgstr "не вдалося визначити фактичний тип результату для функції \"%s\" оголошеної як, та, котра повертає тип %s" -#: utils/fmgr/funcapi.c:1652 utils/fmgr/funcapi.c:1684 +#: utils/fmgr/funcapi.c:1686 utils/fmgr/funcapi.c:1718 #, c-format msgid "number of aliases does not match number of columns" msgstr "кількість псевдонімів не відповідає кількості стовпців" -#: utils/fmgr/funcapi.c:1678 +#: utils/fmgr/funcapi.c:1712 #, c-format msgid "no column alias was provided" msgstr "жодного псевдоніму для стовпця не було надано" -#: utils/fmgr/funcapi.c:1702 +#: utils/fmgr/funcapi.c:1736 #, c-format msgid "could not determine row description for function returning record" msgstr "не вдалося визначити опис рядка для функції, що повертає запис" @@ -24350,128 +24354,128 @@ msgid "too many connections for role \"%s\"" msgstr "занадто багато підключень для ролі \"%s\"" -#: utils/init/miscinit.c:796 +#: utils/init/miscinit.c:804 #, c-format msgid "permission denied to set session authorization" msgstr "немає прав для встановлення авторизації в сеансі" -#: utils/init/miscinit.c:879 +#: utils/init/miscinit.c:887 #, c-format msgid "invalid role OID: %u" msgstr "неприпустимий OID ролі: %u" -#: utils/init/miscinit.c:933 +#: utils/init/miscinit.c:941 #, c-format msgid "database system is shut down" msgstr "система бази даних вимкнена" -#: utils/init/miscinit.c:1020 +#: utils/init/miscinit.c:1028 #, c-format msgid "could not create lock file \"%s\": %m" msgstr "не вдалося створити файл блокування \"%s\": %m" -#: utils/init/miscinit.c:1034 +#: utils/init/miscinit.c:1042 #, c-format msgid "could not open lock file \"%s\": %m" msgstr "не вдалося відкрити файл блокування \"%s\": %m" -#: utils/init/miscinit.c:1041 +#: utils/init/miscinit.c:1049 #, c-format msgid "could not read lock file \"%s\": %m" msgstr "не вдалося прочитати файл блокування \"%s\": %m" -#: utils/init/miscinit.c:1050 +#: utils/init/miscinit.c:1058 #, c-format msgid "lock file \"%s\" is empty" msgstr "файл блокування \"%s\" пустий" -#: utils/init/miscinit.c:1051 +#: utils/init/miscinit.c:1059 #, c-format msgid "Either another server is starting, or the lock file is the remnant of a previous server startup crash." msgstr "Або зараз запускається інший сервер, або цей файл блокування залишився в результаті збою під час попереднього запуску." -#: utils/init/miscinit.c:1095 +#: utils/init/miscinit.c:1103 #, c-format msgid "lock file \"%s\" already exists" msgstr "файл блокування \"%s\" вже існує" -#: utils/init/miscinit.c:1099 +#: utils/init/miscinit.c:1107 #, c-format msgid "Is another postgres (PID %d) running in data directory \"%s\"?" msgstr "Інший postgres (PID %d) працює з каталогом даних \"%s\"?" -#: utils/init/miscinit.c:1101 +#: utils/init/miscinit.c:1109 #, c-format msgid "Is another postmaster (PID %d) running in data directory \"%s\"?" msgstr "Інший postmaster (PID %d) працює з каталогом даних \"%s\"?" -#: utils/init/miscinit.c:1104 +#: utils/init/miscinit.c:1112 #, c-format msgid "Is another postgres (PID %d) using socket file \"%s\"?" msgstr "Інший postgres (PID %d) використовує файл сокету \"%s\"?" -#: utils/init/miscinit.c:1106 +#: utils/init/miscinit.c:1114 #, c-format msgid "Is another postmaster (PID %d) using socket file \"%s\"?" msgstr "Інший postmaster (PID %d) використовує файл сокету \"%s\"?" -#: utils/init/miscinit.c:1157 +#: utils/init/miscinit.c:1165 #, c-format msgid "could not remove old lock file \"%s\": %m" msgstr "не вдалося видалити старий файл блокування \"%s\": %m" -#: utils/init/miscinit.c:1159 +#: utils/init/miscinit.c:1167 #, c-format msgid "The file seems accidentally left over, but it could not be removed. Please remove the file by hand and try again." msgstr "Здається, файл залишився випадково, але видалити його не вийшло. Будь-ласка, видаліть файл вручну або спробуйте знову." -#: utils/init/miscinit.c:1196 utils/init/miscinit.c:1210 -#: utils/init/miscinit.c:1221 +#: utils/init/miscinit.c:1204 utils/init/miscinit.c:1218 +#: utils/init/miscinit.c:1229 #, c-format msgid "could not write lock file \"%s\": %m" msgstr "не вдалося записати файл блокування \"%s\": %m" -#: utils/init/miscinit.c:1332 utils/init/miscinit.c:1474 utils/misc/guc.c:10088 +#: utils/init/miscinit.c:1340 utils/init/miscinit.c:1482 utils/misc/guc.c:10096 #, c-format msgid "could not read from file \"%s\": %m" msgstr "не вдалося прочитати з файлу \"%s\": %m" -#: utils/init/miscinit.c:1462 +#: utils/init/miscinit.c:1470 #, c-format msgid "could not open file \"%s\": %m; continuing anyway" msgstr "не вдалося відкрити файл \"%s\": %m; все одно продовжується" -#: utils/init/miscinit.c:1487 +#: utils/init/miscinit.c:1495 #, c-format msgid "lock file \"%s\" contains wrong PID: %ld instead of %ld" msgstr "файл блокування \"%s\" містить неправильний PID: %ld замість %ld" -#: utils/init/miscinit.c:1526 utils/init/miscinit.c:1542 +#: utils/init/miscinit.c:1534 utils/init/miscinit.c:1550 #, c-format msgid "\"%s\" is not a valid data directory" msgstr "\"%s\" не є припустимим каталогом даних" -#: utils/init/miscinit.c:1528 +#: utils/init/miscinit.c:1536 #, c-format msgid "File \"%s\" is missing." msgstr "Файл \"%s\" пропущено." -#: utils/init/miscinit.c:1544 +#: utils/init/miscinit.c:1552 #, c-format msgid "File \"%s\" does not contain valid data." msgstr "Файл \"%s\" не містить припустимих даних." -#: utils/init/miscinit.c:1546 +#: utils/init/miscinit.c:1554 #, c-format msgid "You might need to initdb." msgstr "Можливо, вам слід виконати initdb." -#: utils/init/miscinit.c:1554 +#: utils/init/miscinit.c:1562 #, c-format msgid "The data directory was initialized by PostgreSQL version %s, which is not compatible with this version %s." msgstr "Каталог даних ініціалізований сервером PostgreSQL версії %s, не сумісною з цією версією %s." -#: utils/init/miscinit.c:1621 +#: utils/init/miscinit.c:1629 #, c-format msgid "loaded library \"%s\"" msgstr "завантажена бібліотека \"%s\"" @@ -25032,8 +25036,8 @@ msgstr "Примусова синхронізація оновлень на диск." #: utils/misc/guc.c:1186 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." -msgstr "Сервер буде використовувати системний виклик fsync() в декількох місцях, щоб впевнитись, що оновлення фізично записані на диск. Це дозволить привести кластер бази даних в узгоджений стан після аварійного завершення роботи операційної системи або апаратного забезпечення." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgstr "Сервер буде використовувати системний виклик fsync() в декількох місцях, щоб переконатися, що оновлення фізично записані на диск. Це гарантує, що кластер баз даних відновиться до узгодженого стану після аварійного завершення роботи операційної системи чи апаратного збою." #: utils/misc/guc.c:1197 msgid "Continues processing after a checksum failure." @@ -26620,7 +26624,7 @@ #: utils/misc/guc.c:6992 utils/misc/guc.c:7772 utils/misc/guc.c:7825 #: utils/misc/guc.c:7876 utils/misc/guc.c:8209 utils/misc/guc.c:8976 -#: utils/misc/guc.c:9248 utils/misc/guc.c:10921 +#: utils/misc/guc.c:9255 utils/misc/guc.c:10929 #, c-format msgid "unrecognized configuration parameter \"%s\"" msgstr "нерозпізнаний параметр конфігурації \"%s\"" @@ -26642,7 +26646,7 @@ msgid "parameter \"%s\" cannot be changed now" msgstr "параметр \"%s\" не може бути змінений зараз" -#: utils/misc/guc.c:7058 utils/misc/guc.c:7105 utils/misc/guc.c:10937 +#: utils/misc/guc.c:7058 utils/misc/guc.c:7105 utils/misc/guc.c:10945 #, c-format msgid "permission denied to set parameter \"%s\"" msgstr "немає прав для встановлення параметру \"%s\"" @@ -26657,7 +26661,7 @@ msgid "cannot set parameter \"%s\" within security-definer function" msgstr "параметр \"%s\" не можна встановити в межах функції безпеки" -#: utils/misc/guc.c:7780 utils/misc/guc.c:7830 utils/misc/guc.c:9255 +#: utils/misc/guc.c:7780 utils/misc/guc.c:7830 utils/misc/guc.c:9262 #, c-format msgid "must be superuser or a member of pg_read_all_settings to examine \"%s\"" msgstr "щоб дослідити \"%s\" потрібно бути суперкористувачем або учасником ролі pg_read_all_settings" @@ -26697,87 +26701,87 @@ msgid "attempt to redefine parameter \"%s\"" msgstr "спроба перевизначити параметр \"%s\"" -#: utils/misc/guc.c:10476 +#: utils/misc/guc.c:10484 #, c-format msgid "while setting parameter \"%s\" to \"%s\"" msgstr "під час налаштування параметру \"%s\" на \"%s\"" -#: utils/misc/guc.c:10544 +#: utils/misc/guc.c:10552 #, c-format msgid "parameter \"%s\" could not be set" msgstr "параметр \"%s\" не вдалося встановити" -#: utils/misc/guc.c:10636 +#: utils/misc/guc.c:10644 #, c-format msgid "could not parse setting for parameter \"%s\"" msgstr "не вдалося аналізувати налаштування параметру \"%s\"" -#: utils/misc/guc.c:10999 utils/misc/guc.c:11033 +#: utils/misc/guc.c:11007 utils/misc/guc.c:11041 #, c-format msgid "invalid value for parameter \"%s\": %d" msgstr "неприпустиме значення для параметра \"%s\": %d" -#: utils/misc/guc.c:11067 +#: utils/misc/guc.c:11075 #, c-format msgid "invalid value for parameter \"%s\": %g" msgstr "неприпустиме значення для параметра \"%s\": %g" -#: utils/misc/guc.c:11354 +#: utils/misc/guc.c:11362 #, c-format msgid "\"temp_buffers\" cannot be changed after any temporary tables have been accessed in the session." msgstr "параметр \"temp_buffers\" не можна змінити після того, як тимчасові таблиці отримали доступ в сеансі." -#: utils/misc/guc.c:11366 +#: utils/misc/guc.c:11374 #, c-format msgid "Bonjour is not supported by this build" msgstr "Bonjour не підтримується даною збіркою" -#: utils/misc/guc.c:11379 +#: utils/misc/guc.c:11387 #, c-format msgid "SSL is not supported by this build" msgstr "SSL не підтримується даною збіркою" -#: utils/misc/guc.c:11391 +#: utils/misc/guc.c:11399 #, c-format msgid "Cannot enable parameter when \"log_statement_stats\" is true." msgstr "Не можна ввімкнути параметр, коли \"log_statement_stats\" дорівнює true." -#: utils/misc/guc.c:11403 +#: utils/misc/guc.c:11411 #, c-format msgid "Cannot enable \"log_statement_stats\" when \"log_parser_stats\", \"log_planner_stats\", or \"log_executor_stats\" is true." msgstr "Не можна ввімкнути \"log_statement_stats\", коли \"log_parser_stats\", \"log_planner_stats\", або \"log_executor_stats\" дорівнюють true." -#: utils/misc/guc.c:11633 +#: utils/misc/guc.c:11641 #, c-format msgid "effective_io_concurrency must be set to 0 on platforms that lack posix_fadvise()." msgstr "значення effective_io_concurrency повинне дорівнювати 0 (нулю) на платформах, де відсутній posix_fadvise()." -#: utils/misc/guc.c:11646 +#: utils/misc/guc.c:11654 #, c-format msgid "maintenance_io_concurrency must be set to 0 on platforms that lack posix_fadvise()." msgstr "maintenance_io_concurrency повинне бути встановлене на 0, на платформах які не мають posix_fadvise()." -#: utils/misc/guc.c:11762 +#: utils/misc/guc.c:11770 #, c-format msgid "invalid character" msgstr "неприпустимий символ" -#: utils/misc/guc.c:11822 +#: utils/misc/guc.c:11830 #, c-format msgid "recovery_target_timeline is not a valid number." msgstr "recovery_target_timeline не є допустимим числом." -#: utils/misc/guc.c:11862 +#: utils/misc/guc.c:11870 #, c-format msgid "multiple recovery targets specified" msgstr "вказано декілька цілей відновлення" -#: utils/misc/guc.c:11863 +#: utils/misc/guc.c:11871 #, c-format msgid "At most one of recovery_target, recovery_target_lsn, recovery_target_name, recovery_target_time, recovery_target_xid may be set." msgstr "Максимум один із recovery_target, recovery_target_lsn, recovery_target_name, recovery_target_time, recovery_target_xid може бути встановлений." -#: utils/misc/guc.c:11871 +#: utils/misc/guc.c:11879 #, c-format msgid "The only allowed value is \"immediate\"." msgstr "Єдиним дозволеним значенням є \"immediate\"." @@ -26792,8 +26796,8 @@ msgid "query-specified return tuple and function return type are not compatible" msgstr "вказаний у запиті кортеж і функція повертаючого типу несумісні" -#: utils/misc/pg_controldata.c:60 utils/misc/pg_controldata.c:138 -#: utils/misc/pg_controldata.c:241 utils/misc/pg_controldata.c:306 +#: utils/misc/pg_controldata.c:63 utils/misc/pg_controldata.c:143 +#: utils/misc/pg_controldata.c:248 utils/misc/pg_controldata.c:315 #, c-format msgid "calculated CRC checksum does not match value stored in file" msgstr "обчислена контрольна сума CRC не відповідає значенню, збереженому у файлі" diff -Nru postgresql-13-13.13/src/backend/po/zh_CN.po postgresql-13-13.14/src/backend/po/zh_CN.po --- postgresql-13-13.13/src/backend/po/zh_CN.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/po/zh_CN.po 2024-02-05 21:47:02.000000000 +0000 @@ -24615,7 +24615,7 @@ msgstr "强制和磁盘同步更新" #: utils/misc/guc.c:1127 -msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This insures that a database cluster will recover to a consistent state after an operating system or hardware crash." +msgid "The server will use the fsync() system call in several places to make sure that updates are physically written to disk. This ensures that a database cluster will recover to a consistent state after an operating system or hardware crash." msgstr "服务器将在多个位置使用系统调用fsync()来确定更新操作已经将数据写入磁盘.这将确保在操作系统或硬件崩溃后数据库集群将恢复到一个一致性状态. " #: utils/misc/guc.c:1138 diff -Nru postgresql-13-13.13/src/backend/port/win32/socket.c postgresql-13-13.14/src/backend/port/win32/socket.c --- postgresql-13-13.13/src/backend/port/win32/socket.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/port/win32/socket.c 2024-02-05 21:47:02.000000000 +0000 @@ -290,6 +290,7 @@ if (ioctlsocket(s, FIONBIO, &on)) { TranslateSocketError(); + closesocket(s); return INVALID_SOCKET; } errno = 0; diff -Nru postgresql-13-13.13/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c postgresql-13-13.14/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c --- postgresql-13-13.13/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/replication/libpqwalreceiver/libpqwalreceiver.c 2024-02-05 21:47:02.000000000 +0000 @@ -358,6 +358,10 @@ "the primary server: %s", pchomp(PQerrorMessage(conn->streamConn))))); } + /* + * IDENTIFY_SYSTEM returns 3 columns in 9.3 and earlier, and 4 columns in + * 9.4 and onwards. + */ if (PQnfields(res) < 3 || PQntuples(res) != 1) { int ntuples = PQntuples(res); @@ -367,7 +371,7 @@ ereport(ERROR, (errmsg("invalid response from primary server"), errdetail("Could not identify system: got %d rows and %d fields, expected %d rows and %d or more fields.", - ntuples, nfields, 3, 1))); + ntuples, nfields, 1, 3))); } primary_sysid = pstrdup(PQgetvalue(res, 0, 0)); *primary_tli = pg_strtoint32(PQgetvalue(res, 0, 1)); diff -Nru postgresql-13-13.13/src/backend/replication/logical/tablesync.c postgresql-13-13.14/src/backend/replication/logical/tablesync.c --- postgresql-13-13.13/src/backend/replication/logical/tablesync.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/replication/logical/tablesync.c 2024-02-05 21:47:02.000000000 +0000 @@ -457,15 +457,25 @@ /* Now safe to release the LWLock */ LWLockRelease(LogicalRepWorkerLock); + if (started_tx) + { + /* + * We must commit the existing transaction to release + * the existing locks before entering a busy loop. + * This is required to avoid any undetected deadlocks + * due to any existing lock as deadlock detector won't + * be able to detect the waits on the latch. + */ + CommitTransactionCommand(); + pgstat_report_stat(false); + } + /* * Enter busy loop and wait for synchronization worker to * reach expected state (or die trying). */ - if (!started_tx) - { - StartTransactionCommand(); - started_tx = true; - } + StartTransactionCommand(); + started_tx = true; wait_for_relation_state_change(rstate->relid, SUBREL_STATE_SYNCDONE); diff -Nru postgresql-13-13.13/src/backend/storage/ipc/procarray.c postgresql-13-13.14/src/backend/storage/ipc/procarray.c --- postgresql-13-13.13/src/backend/storage/ipc/procarray.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/storage/ipc/procarray.c 2024-02-05 21:47:02.000000000 +0000 @@ -1522,8 +1522,7 @@ * but since PGPROC has only a limited cache area for subxact XIDs, full * information may not be available. If we find any overflowed subxid arrays, * we have to mark the snapshot's subxid data as overflowed, and extra work - * *may* need to be done to determine what's running (see XidInMVCCSnapshot() - * in heapam_visibility.c). + * *may* need to be done to determine what's running (see XidInMVCCSnapshot()). * * We also update the following backend-global variables: * TransactionXmin: the oldest xmin of any snapshot in use in the diff -Nru postgresql-13-13.13/src/backend/storage/lmgr/lwlock.c postgresql-13-13.14/src/backend/storage/lmgr/lwlock.c --- postgresql-13-13.13/src/backend/storage/lmgr/lwlock.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/storage/lmgr/lwlock.c 2024-02-05 21:47:02.000000000 +0000 @@ -999,6 +999,15 @@ } /* + * Signal that the process isn't on the wait list anymore. This allows + * LWLockDequeueSelf() to remove itself of the waitlist with a + * proclist_delete(), rather than having to check if it has been + * removed from the list. + */ + Assert(waiter->lwWaiting == LW_WS_WAITING); + waiter->lwWaiting = LW_WS_PENDING_WAKEUP; + + /* * Once we've woken up an exclusive lock, there's no point in waking * up anybody else. */ @@ -1055,7 +1064,7 @@ * another lock. */ pg_write_barrier(); - waiter->lwWaiting = false; + waiter->lwWaiting = LW_WS_NOT_WAITING; PGSemaphoreUnlock(waiter->sem); } } @@ -1076,7 +1085,7 @@ if (MyProc == NULL) elog(PANIC, "cannot wait without a PGPROC structure"); - if (MyProc->lwWaiting) + if (MyProc->lwWaiting != LW_WS_NOT_WAITING) elog(PANIC, "queueing for lock while waiting on another one"); LWLockWaitListLock(lock); @@ -1084,7 +1093,7 @@ /* setting the flag is protected by the spinlock */ pg_atomic_fetch_or_u32(&lock->state, LW_FLAG_HAS_WAITERS); - MyProc->lwWaiting = true; + MyProc->lwWaiting = LW_WS_WAITING; MyProc->lwWaitMode = mode; /* LW_WAIT_UNTIL_FREE waiters are always at the front of the queue */ @@ -1112,8 +1121,7 @@ static void LWLockDequeueSelf(LWLock *lock) { - bool found = false; - proclist_mutable_iter iter; + bool on_waitlist; #ifdef LWLOCK_STATS lwlock_stats *lwstats; @@ -1126,18 +1134,13 @@ LWLockWaitListLock(lock); /* - * Can't just remove ourselves from the list, but we need to iterate over - * all entries as somebody else could have dequeued us. - */ - proclist_foreach_modify(iter, &lock->waiters, lwWaitLink) - { - if (iter.cur == MyProc->pgprocno) - { - found = true; - proclist_delete(&lock->waiters, iter.cur, lwWaitLink); - break; - } - } + * Remove ourselves from the waitlist, unless we've already been + * removed. The removal happens with the wait list lock held, so there's + * no race in this check. + */ + on_waitlist = MyProc->lwWaiting == LW_WS_WAITING; + if (on_waitlist) + proclist_delete(&lock->waiters, MyProc->pgprocno, lwWaitLink); if (proclist_is_empty(&lock->waiters) && (pg_atomic_read_u32(&lock->state) & LW_FLAG_HAS_WAITERS) != 0) @@ -1149,8 +1152,8 @@ LWLockWaitListUnlock(lock); /* clear waiting state again, nice for debugging */ - if (found) - MyProc->lwWaiting = false; + if (on_waitlist) + MyProc->lwWaiting = LW_WS_NOT_WAITING; else { int extraWaits = 0; @@ -1174,7 +1177,7 @@ for (;;) { PGSemaphoreLock(MyProc->sem); - if (!MyProc->lwWaiting) + if (MyProc->lwWaiting == LW_WS_NOT_WAITING) break; extraWaits++; } @@ -1325,7 +1328,7 @@ for (;;) { PGSemaphoreLock(proc->sem); - if (!proc->lwWaiting) + if (proc->lwWaiting == LW_WS_NOT_WAITING) break; extraWaits++; } @@ -1490,7 +1493,7 @@ for (;;) { PGSemaphoreLock(proc->sem); - if (!proc->lwWaiting) + if (proc->lwWaiting == LW_WS_NOT_WAITING) break; extraWaits++; } @@ -1706,7 +1709,7 @@ for (;;) { PGSemaphoreLock(proc->sem); - if (!proc->lwWaiting) + if (proc->lwWaiting == LW_WS_NOT_WAITING) break; extraWaits++; } @@ -1787,6 +1790,10 @@ proclist_delete(&lock->waiters, iter.cur, lwWaitLink); proclist_push_tail(&wakeup, iter.cur, lwWaitLink); + + /* see LWLockWakeup() */ + Assert(waiter->lwWaiting == LW_WS_WAITING); + waiter->lwWaiting = LW_WS_PENDING_WAKEUP; } /* We are done updating shared state of the lock itself. */ @@ -1802,7 +1809,7 @@ proclist_delete(&wakeup, iter.cur, lwWaitLink); /* check comment in LWLockWakeup() about this barrier */ pg_write_barrier(); - waiter->lwWaiting = false; + waiter->lwWaiting = LW_WS_NOT_WAITING; PGSemaphoreUnlock(waiter->sem); } } diff -Nru postgresql-13-13.13/src/backend/storage/lmgr/proc.c postgresql-13-13.14/src/backend/storage/lmgr/proc.c --- postgresql-13-13.13/src/backend/storage/lmgr/proc.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/storage/lmgr/proc.c 2024-02-05 21:47:02.000000000 +0000 @@ -402,7 +402,7 @@ /* NB -- autovac launcher intentionally does not set IS_AUTOVACUUM */ if (IsAutoVacuumWorkerProcess()) MyPgXact->vacuumFlags |= PROC_IS_AUTOVACUUM; - MyProc->lwWaiting = false; + MyProc->lwWaiting = LW_WS_NOT_WAITING; MyProc->lwWaitMode = 0; MyProc->waitLock = NULL; MyProc->waitProcLock = NULL; @@ -582,7 +582,7 @@ MyProc->delayChkpt = false; MyProc->delayChkptEnd = false; MyPgXact->vacuumFlags = 0; - MyProc->lwWaiting = false; + MyProc->lwWaiting = LW_WS_NOT_WAITING; MyProc->lwWaitMode = 0; MyProc->waitLock = NULL; MyProc->waitProcLock = NULL; diff -Nru postgresql-13-13.13/src/backend/utils/adt/timestamp.c postgresql-13-13.14/src/backend/utils/adt/timestamp.c --- postgresql-13-13.13/src/backend/utils/adt/timestamp.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/utils/adt/timestamp.c 2024-02-05 21:47:02.000000000 +0000 @@ -22,6 +22,7 @@ #include "access/xact.h" #include "catalog/pg_type.h" +#include "common/int.h" #include "common/int128.h" #include "funcapi.h" #include "libpq/pqformat.h" @@ -2887,8 +2888,16 @@ (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), errmsg("timestamp out of range"))); - /* Add days by converting to and from Julian */ - julian = date2j(tm->tm_year, tm->tm_mon, tm->tm_mday) + span->day; + /* + * Add days by converting to and from Julian. We need an overflow + * check here since j2date expects a non-negative integer input. + */ + julian = date2j(tm->tm_year, tm->tm_mon, tm->tm_mday); + if (pg_add_s32_overflow(julian, span->day, &julian) || + julian < 0) + ereport(ERROR, + (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), + errmsg("timestamp out of range"))); j2date(julian, &tm->tm_year, &tm->tm_mon, &tm->tm_mday); if (tm2timestamp(tm, fsec, NULL, ×tamp) != 0) @@ -2995,8 +3004,19 @@ (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), errmsg("timestamp out of range"))); - /* Add days by converting to and from Julian */ - julian = date2j(tm->tm_year, tm->tm_mon, tm->tm_mday) + span->day; + /* + * Add days by converting to and from Julian. We need an overflow + * check here since j2date expects a non-negative integer input. + * In practice though, it will give correct answers for small + * negative Julian dates; we should allow -1 to avoid + * timezone-dependent failures, as discussed in timestamp.h. + */ + julian = date2j(tm->tm_year, tm->tm_mon, tm->tm_mday); + if (pg_add_s32_overflow(julian, span->day, &julian) || + julian < -1) + ereport(ERROR, + (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), + errmsg("timestamp out of range"))); j2date(julian, &tm->tm_year, &tm->tm_mon, &tm->tm_mday); tz = DetermineTimeZoneOffset(tm, session_timezone); @@ -3184,19 +3204,13 @@ result = (Interval *) palloc(sizeof(Interval)); result_double = span->month * factor; - if (isnan(result_double) || - result_double > INT_MAX || result_double < INT_MIN) - ereport(ERROR, - (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), - errmsg("interval out of range"))); + if (isnan(result_double) || !FLOAT8_FITS_IN_INT32(result_double)) + goto out_of_range; result->month = (int32) result_double; result_double = span->day * factor; - if (isnan(result_double) || - result_double > INT_MAX || result_double < INT_MIN) - ereport(ERROR, - (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), - errmsg("interval out of range"))); + if (isnan(result_double) || !FLOAT8_FITS_IN_INT32(result_double)) + goto out_of_range; result->day = (int32) result_double; /* @@ -3230,20 +3244,30 @@ */ if (Abs(sec_remainder) >= SECS_PER_DAY) { - result->day += (int) (sec_remainder / SECS_PER_DAY); + if (pg_add_s32_overflow(result->day, + (int) (sec_remainder / SECS_PER_DAY), + &result->day)) + goto out_of_range; sec_remainder -= (int) (sec_remainder / SECS_PER_DAY) * SECS_PER_DAY; } /* cascade units down */ - result->day += (int32) month_remainder_days; + if (pg_add_s32_overflow(result->day, (int32) month_remainder_days, + &result->day)) + goto out_of_range; result_double = rint(span->time * factor + sec_remainder * USECS_PER_SEC); if (isnan(result_double) || !FLOAT8_FITS_IN_INT64(result_double)) - ereport(ERROR, - (errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), - errmsg("interval out of range"))); + goto out_of_range; result->time = (int64) result_double; PG_RETURN_INTERVAL_P(result); + +out_of_range: + ereport(ERROR, + errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), + errmsg("interval out of range")); + + PG_RETURN_NULL(); /* keep compiler quiet */ } Datum @@ -3262,7 +3286,8 @@ Interval *span = PG_GETARG_INTERVAL_P(0); float8 factor = PG_GETARG_FLOAT8(1); double month_remainder_days, - sec_remainder; + sec_remainder, + result_double; int32 orig_month = span->month, orig_day = span->day; Interval *result; @@ -3274,8 +3299,15 @@ (errcode(ERRCODE_DIVISION_BY_ZERO), errmsg("division by zero"))); - result->month = (int32) (span->month / factor); - result->day = (int32) (span->day / factor); + result_double = span->month / factor; + if (isnan(result_double) || !FLOAT8_FITS_IN_INT32(result_double)) + goto out_of_range; + result->month = (int32) result_double; + + result_double = span->day / factor; + if (isnan(result_double) || !FLOAT8_FITS_IN_INT32(result_double)) + goto out_of_range; + result->day = (int32) result_double; /* * Fractional months full days into days. See comment in interval_mul(). @@ -3287,15 +3319,30 @@ sec_remainder = TSROUND(sec_remainder); if (Abs(sec_remainder) >= SECS_PER_DAY) { - result->day += (int) (sec_remainder / SECS_PER_DAY); + if (pg_add_s32_overflow(result->day, + (int) (sec_remainder / SECS_PER_DAY), + &result->day)) + goto out_of_range; sec_remainder -= (int) (sec_remainder / SECS_PER_DAY) * SECS_PER_DAY; } /* cascade units down */ - result->day += (int32) month_remainder_days; - result->time = rint(span->time / factor + sec_remainder * USECS_PER_SEC); + if (pg_add_s32_overflow(result->day, (int32) month_remainder_days, + &result->day)) + goto out_of_range; + result_double = rint(span->time / factor + sec_remainder * USECS_PER_SEC); + if (isnan(result_double) || !FLOAT8_FITS_IN_INT64(result_double)) + goto out_of_range; + result->time = (int64) result_double; PG_RETURN_INTERVAL_P(result); + +out_of_range: + ereport(ERROR, + errcode(ERRCODE_DATETIME_VALUE_OUT_OF_RANGE), + errmsg("interval out of range")); + + PG_RETURN_NULL(); /* keep compiler quiet */ } diff -Nru postgresql-13-13.13/src/backend/utils/adt/xml.c postgresql-13-13.14/src/backend/utils/adt/xml.c --- postgresql-13-13.13/src/backend/utils/adt/xml.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/utils/adt/xml.c 2024-02-05 21:47:02.000000000 +0000 @@ -65,6 +65,16 @@ #if LIBXML_VERSION >= 20704 #define HAVE_XMLSTRUCTUREDERRORCONTEXT 1 #endif + +/* + * libxml2 2.12 decided to insert "const" into the error handler API. + */ +#if LIBXML_VERSION >= 21200 +#define PgXmlErrorPtr const xmlError * +#else +#define PgXmlErrorPtr xmlErrorPtr +#endif + #endif /* USE_LIBXML */ #include "access/htup_details.h" @@ -119,7 +129,7 @@ static xmlParserInputPtr xmlPgEntityLoader(const char *URL, const char *ID, xmlParserCtxtPtr ctxt); -static void xml_errorHandler(void *data, xmlErrorPtr error); +static void xml_errorHandler(void *data, PgXmlErrorPtr error); static void xml_ereport_by_code(int level, int sqlcode, const char *msg, int errcode); static void chopStringInfoNewlines(StringInfo str); @@ -1750,7 +1760,7 @@ * Error handler for libxml errors and warnings */ static void -xml_errorHandler(void *data, xmlErrorPtr error) +xml_errorHandler(void *data, PgXmlErrorPtr error) { PgXmlErrorContext *xmlerrcxt = (PgXmlErrorContext *) data; xmlParserCtxtPtr ctxt = (xmlParserCtxtPtr) error->ctxt; diff -Nru postgresql-13-13.13/src/backend/utils/cache/catcache.c postgresql-13-13.14/src/backend/utils/cache/catcache.c --- postgresql-13-13.13/src/backend/utils/cache/catcache.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/utils/cache/catcache.c 2024-02-05 21:47:02.000000000 +0000 @@ -89,10 +89,10 @@ static void CatCacheRemoveCTup(CatCache *cache, CatCTup *ct); static void CatCacheRemoveCList(CatCache *cache, CatCList *cl); static void CatalogCacheInitializeCache(CatCache *cache); -static CatCTup *CatalogCacheCreateEntry(CatCache *cache, HeapTuple ntp, +static CatCTup *CatalogCacheCreateEntry(CatCache *cache, + HeapTuple ntp, SysScanDesc scandesc, Datum *arguments, - uint32 hashValue, Index hashIndex, - bool negative); + uint32 hashValue, Index hashIndex); static void CatCacheFreeKeys(TupleDesc tupdesc, int nkeys, int *attnos, Datum *keys); @@ -1322,6 +1322,7 @@ SysScanDesc scandesc; HeapTuple ntp; CatCTup *ct; + bool stale; Datum arguments[CATCACHE_MAXKEYS]; /* Initialize local parameter array */ @@ -1331,16 +1332,6 @@ arguments[3] = v4; /* - * Ok, need to make a lookup in the relation, copy the scankey and fill - * out any per-call fields. - */ - memcpy(cur_skey, cache->cc_skey, sizeof(ScanKeyData) * nkeys); - cur_skey[0].sk_argument = v1; - cur_skey[1].sk_argument = v2; - cur_skey[2].sk_argument = v3; - cur_skey[3].sk_argument = v4; - - /* * Tuple was not found in cache, so we have to try to retrieve it directly * from the relation. If found, we will add it to the cache; if not * found, we will add a negative cache entry instead. @@ -1354,31 +1345,57 @@ * will eventually age out of the cache, so there's no functional problem. * This case is rare enough that it's not worth expending extra cycles to * detect. + * + * Another case, which we *must* handle, is that the tuple could become + * outdated during CatalogCacheCreateEntry's attempt to detoast it (since + * AcceptInvalidationMessages can run during TOAST table access). We do + * not want to return already-stale catcache entries, so we loop around + * and do the table scan again if that happens. */ relation = table_open(cache->cc_reloid, AccessShareLock); - scandesc = systable_beginscan(relation, - cache->cc_indexoid, - IndexScanOK(cache, cur_skey), - NULL, - nkeys, - cur_skey); - - ct = NULL; - - while (HeapTupleIsValid(ntp = systable_getnext(scandesc))) - { - ct = CatalogCacheCreateEntry(cache, ntp, arguments, - hashValue, hashIndex, - false); - /* immediately set the refcount to 1 */ - ResourceOwnerEnlargeCatCacheRefs(CurrentResourceOwner); - ct->refcount++; - ResourceOwnerRememberCatCacheRef(CurrentResourceOwner, &ct->tuple); - break; /* assume only one match */ - } + do + { + /* + * Ok, need to make a lookup in the relation, copy the scankey and + * fill out any per-call fields. (We must re-do this when retrying, + * because systable_beginscan scribbles on the scankey.) + */ + memcpy(cur_skey, cache->cc_skey, sizeof(ScanKeyData) * nkeys); + cur_skey[0].sk_argument = v1; + cur_skey[1].sk_argument = v2; + cur_skey[2].sk_argument = v3; + cur_skey[3].sk_argument = v4; - systable_endscan(scandesc); + scandesc = systable_beginscan(relation, + cache->cc_indexoid, + IndexScanOK(cache, cur_skey), + NULL, + nkeys, + cur_skey); + + ct = NULL; + stale = false; + + while (HeapTupleIsValid(ntp = systable_getnext(scandesc))) + { + ct = CatalogCacheCreateEntry(cache, ntp, scandesc, NULL, + hashValue, hashIndex); + /* upon failure, we must start the scan over */ + if (ct == NULL) + { + stale = true; + break; + } + /* immediately set the refcount to 1 */ + ResourceOwnerEnlargeCatCacheRefs(CurrentResourceOwner); + ct->refcount++; + ResourceOwnerRememberCatCacheRef(CurrentResourceOwner, &ct->tuple); + break; /* assume only one match */ + } + + systable_endscan(scandesc); + } while (stale); table_close(relation, AccessShareLock); @@ -1397,9 +1414,11 @@ if (IsBootstrapProcessingMode()) return NULL; - ct = CatalogCacheCreateEntry(cache, NULL, arguments, - hashValue, hashIndex, - true); + ct = CatalogCacheCreateEntry(cache, NULL, NULL, arguments, + hashValue, hashIndex); + + /* Creating a negative cache entry shouldn't fail */ + Assert(ct != NULL); CACHE_elog(DEBUG2, "SearchCatCache(%s): Contains %d/%d tuples", cache->cc_relname, cache->cc_ntup, CacheHdr->ch_ntup); @@ -1606,7 +1625,8 @@ * We have to bump the member refcounts temporarily to ensure they won't * get dropped from the cache while loading other members. We use a PG_TRY * block to ensure we can undo those refcounts if we get an error before - * we finish constructing the CatCList. + * we finish constructing the CatCList. ctlist must be valid throughout + * the PG_TRY block. */ ResourceOwnerEnlargeCatCacheListRefs(CurrentResourceOwner); @@ -1617,83 +1637,113 @@ ScanKeyData cur_skey[CATCACHE_MAXKEYS]; Relation relation; SysScanDesc scandesc; - - /* - * Ok, need to make a lookup in the relation, copy the scankey and - * fill out any per-call fields. - */ - memcpy(cur_skey, cache->cc_skey, sizeof(ScanKeyData) * cache->cc_nkeys); - cur_skey[0].sk_argument = v1; - cur_skey[1].sk_argument = v2; - cur_skey[2].sk_argument = v3; - cur_skey[3].sk_argument = v4; + bool stale; relation = table_open(cache->cc_reloid, AccessShareLock); - scandesc = systable_beginscan(relation, - cache->cc_indexoid, - IndexScanOK(cache, cur_skey), - NULL, - nkeys, - cur_skey); - - /* The list will be ordered iff we are doing an index scan */ - ordered = (scandesc->irel != NULL); - - while (HeapTupleIsValid(ntp = systable_getnext(scandesc))) + do { - uint32 hashValue; - Index hashIndex; - bool found = false; - dlist_head *bucket; - /* - * See if there's an entry for this tuple already. + * Ok, need to make a lookup in the relation, copy the scankey and + * fill out any per-call fields. (We must re-do this when + * retrying, because systable_beginscan scribbles on the scankey.) */ - ct = NULL; - hashValue = CatalogCacheComputeTupleHashValue(cache, cache->cc_nkeys, ntp); - hashIndex = HASH_INDEX(hashValue, cache->cc_nbuckets); + memcpy(cur_skey, cache->cc_skey, sizeof(ScanKeyData) * cache->cc_nkeys); + cur_skey[0].sk_argument = v1; + cur_skey[1].sk_argument = v2; + cur_skey[2].sk_argument = v3; + cur_skey[3].sk_argument = v4; + + scandesc = systable_beginscan(relation, + cache->cc_indexoid, + IndexScanOK(cache, cur_skey), + NULL, + nkeys, + cur_skey); - bucket = &cache->cc_bucket[hashIndex]; - dlist_foreach(iter, bucket) - { - ct = dlist_container(CatCTup, cache_elem, iter.cur); + /* The list will be ordered iff we are doing an index scan */ + ordered = (scandesc->irel != NULL); - if (ct->dead || ct->negative) - continue; /* ignore dead and negative entries */ + stale = false; - if (ct->hash_value != hashValue) - continue; /* quickly skip entry if wrong hash val */ - - if (!ItemPointerEquals(&(ct->tuple.t_self), &(ntp->t_self))) - continue; /* not same tuple */ + while (HeapTupleIsValid(ntp = systable_getnext(scandesc))) + { + uint32 hashValue; + Index hashIndex; + bool found = false; + dlist_head *bucket; /* - * Found a match, but can't use it if it belongs to another - * list already + * See if there's an entry for this tuple already. */ - if (ct->c_list) - continue; - - found = true; - break; /* A-OK */ - } - - if (!found) - { - /* We didn't find a usable entry, so make a new one */ - ct = CatalogCacheCreateEntry(cache, ntp, arguments, - hashValue, hashIndex, - false); + ct = NULL; + hashValue = CatalogCacheComputeTupleHashValue(cache, cache->cc_nkeys, ntp); + hashIndex = HASH_INDEX(hashValue, cache->cc_nbuckets); + + bucket = &cache->cc_bucket[hashIndex]; + dlist_foreach(iter, bucket) + { + ct = dlist_container(CatCTup, cache_elem, iter.cur); + + if (ct->dead || ct->negative) + continue; /* ignore dead and negative entries */ + + if (ct->hash_value != hashValue) + continue; /* quickly skip entry if wrong hash val */ + + if (!ItemPointerEquals(&(ct->tuple.t_self), &(ntp->t_self))) + continue; /* not same tuple */ + + /* + * Found a match, but can't use it if it belongs to + * another list already + */ + if (ct->c_list) + continue; + + found = true; + break; /* A-OK */ + } + + if (!found) + { + /* We didn't find a usable entry, so make a new one */ + ct = CatalogCacheCreateEntry(cache, ntp, scandesc, NULL, + hashValue, hashIndex); + /* upon failure, we must start the scan over */ + if (ct == NULL) + { + /* + * Release refcounts on any items we already had. We + * dare not try to free them if they're now + * unreferenced, since an error while doing that would + * result in the PG_CATCH below doing extra refcount + * decrements. Besides, we'll likely re-adopt those + * items in the next iteration, so it's not worth + * complicating matters to try to get rid of them. + */ + foreach(ctlist_item, ctlist) + { + ct = (CatCTup *) lfirst(ctlist_item); + Assert(ct->c_list == NULL); + Assert(ct->refcount > 0); + ct->refcount--; + } + /* Reset ctlist in preparation for new try */ + ctlist = NIL; + stale = true; + break; + } + } + + /* Careful here: add entry to ctlist, then bump its refcount */ + /* This way leaves state correct if lappend runs out of memory */ + ctlist = lappend(ctlist, ct); + ct->refcount++; } - /* Careful here: add entry to ctlist, then bump its refcount */ - /* This way leaves state correct if lappend runs out of memory */ - ctlist = lappend(ctlist, ct); - ct->refcount++; - } - - systable_endscan(scandesc); + systable_endscan(scandesc); + } while (stale); table_close(relation, AccessShareLock); @@ -1801,22 +1851,42 @@ * CatalogCacheCreateEntry * Create a new CatCTup entry, copying the given HeapTuple and other * supplied data into it. The new entry initially has refcount 0. + * + * To create a normal cache entry, ntp must be the HeapTuple just fetched + * from scandesc, and "arguments" is not used. To create a negative cache + * entry, pass NULL for ntp and scandesc; then "arguments" is the cache + * keys to use. In either case, hashValue/hashIndex are the hash values + * computed from the cache keys. + * + * Returns NULL if we attempt to detoast the tuple and observe that it + * became stale. (This cannot happen for a negative entry.) Caller must + * retry the tuple lookup in that case. */ static CatCTup * -CatalogCacheCreateEntry(CatCache *cache, HeapTuple ntp, Datum *arguments, - uint32 hashValue, Index hashIndex, - bool negative) +CatalogCacheCreateEntry(CatCache *cache, HeapTuple ntp, SysScanDesc scandesc, + Datum *arguments, + uint32 hashValue, Index hashIndex) { CatCTup *ct; HeapTuple dtp; MemoryContext oldcxt; - /* negative entries have no tuple associated */ if (ntp) { int i; - Assert(!negative); + /* + * The visibility recheck below essentially never fails during our + * regression tests, and there's no easy way to force it to fail for + * testing purposes. To ensure we have test coverage for the retry + * paths in our callers, make debug builds randomly fail about 0.1% of + * the times through this code path, even when there's no toasted + * fields. + */ +#ifdef USE_ASSERT_CHECKING + if (random() <= (MAX_RANDOM_VALUE / 1000)) + return NULL; +#endif /* * If there are any out-of-line toasted fields in the tuple, expand @@ -1826,7 +1896,20 @@ * something using a slightly stale catcache entry. */ if (HeapTupleHasExternal(ntp)) + { dtp = toast_flatten_tuple(ntp, cache->cc_tupdesc); + + /* + * The tuple could become stale while we are doing toast table + * access (since AcceptInvalidationMessages can run then), so we + * must recheck its visibility afterwards. + */ + if (!systable_recheck_tuple(scandesc, ntp)) + { + heap_freetuple(dtp); + return NULL; + } + } else dtp = ntp; @@ -1865,7 +1948,7 @@ } else { - Assert(negative); + /* Set up keys for a negative cache entry */ oldcxt = MemoryContextSwitchTo(CacheMemoryContext); ct = (CatCTup *) palloc(sizeof(CatCTup)); @@ -1887,7 +1970,7 @@ ct->c_list = NULL; ct->refcount = 0; /* for the moment */ ct->dead = false; - ct->negative = negative; + ct->negative = (ntp == NULL); ct->hash_value = hashValue; dlist_push_head(&cache->cc_bucket[hashIndex], &ct->cache_elem); diff -Nru postgresql-13-13.13/src/backend/utils/error/elog.c postgresql-13-13.14/src/backend/utils/error/elog.c --- postgresql-13-13.13/src/backend/utils/error/elog.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/utils/error/elog.c 2024-02-05 21:47:02.000000000 +0000 @@ -672,6 +672,10 @@ edata->sqlerrcode = ERRCODE_DISK_FULL; break; + case ENOMEM: /* Out of memory */ + edata->sqlerrcode = ERRCODE_OUT_OF_MEMORY; + break; + case ENFILE: /* File table overflow */ case EMFILE: /* Too many open files */ edata->sqlerrcode = ERRCODE_INSUFFICIENT_RESOURCES; diff -Nru postgresql-13-13.13/src/backend/utils/misc/guc.c postgresql-13-13.14/src/backend/utils/misc/guc.c --- postgresql-13-13.13/src/backend/utils/misc/guc.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/backend/utils/misc/guc.c 2024-02-05 21:47:02.000000000 +0000 @@ -1184,7 +1184,7 @@ {"fsync", PGC_SIGHUP, WAL_SETTINGS, gettext_noop("Forces synchronization of updates to disk."), gettext_noop("The server will use the fsync() system call in several places to make " - "sure that updates are physically written to disk. This insures " + "sure that updates are physically written to disk. This ensures " "that a database cluster will recover to a consistent state after " "an operating system or hardware crash.") }, @@ -6980,9 +6980,12 @@ * Other changes might need to affect other workers, so forbid them. */ if (IsInParallelMode() && changeVal && action != GUC_ACTION_SAVE) + { ereport(elevel, (errcode(ERRCODE_INVALID_TRANSACTION_STATE), errmsg("cannot set parameters during a parallel operation"))); + return -1; + } record = find_option(name, true, elevel); if (record == NULL) @@ -7072,6 +7075,10 @@ * backends. This is a tad klugy, but necessary because we * don't re-read the config file during backend start. * + * However, if changeVal is false then plow ahead anyway since + * we are trying to find out if the value is potentially good, + * not actually use it. + * * In EXEC_BACKEND builds, this works differently: we load all * non-default settings from the CONFIG_EXEC_PARAMS file * during backend start. In that case we must accept @@ -7082,7 +7089,7 @@ * started it. is_reload will be true when either situation * applies. */ - if (IsUnderPostmaster && !is_reload) + if (IsUnderPostmaster && changeVal && !is_reload) return -1; } else if (context != PGC_POSTMASTER && diff -Nru postgresql-13-13.13/src/bin/pg_ctl/pg_ctl.c postgresql-13-13.14/src/bin/pg_ctl/pg_ctl.c --- postgresql-13-13.13/src/bin/pg_ctl/pg_ctl.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_ctl/pg_ctl.c 2024-02-05 21:47:02.000000000 +0000 @@ -559,11 +559,11 @@ else close(fd); - cmd = psprintf("\"%s\" /C \"\"%s\" %s%s < \"%s\" >> \"%s\" 2>&1\"", + cmd = psprintf("\"%s\" /D /C \"\"%s\" %s%s < \"%s\" >> \"%s\" 2>&1\"", comspec, exec_path, pgdata_opt, post_opts, DEVNULL, log_file); } else - cmd = psprintf("\"%s\" /C \"\"%s\" %s%s < \"%s\" 2>&1\"", + cmd = psprintf("\"%s\" /D /C \"\"%s\" %s%s < \"%s\" 2>&1\"", comspec, exec_path, pgdata_opt, post_opts, DEVNULL); if (!CreateRestrictedProcess(cmd, &pi, false)) diff -Nru postgresql-13-13.13/src/bin/pg_dump/pg_dump.c postgresql-13-13.14/src/bin/pg_dump/pg_dump.c --- postgresql-13-13.13/src/bin/pg_dump/pg_dump.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_dump/pg_dump.c 2024-02-05 21:47:02.000000000 +0000 @@ -1486,13 +1486,10 @@ addObjectDependency(dobj, ext->dobj.dumpId); /* - * In 9.6 and above, mark the member object to have any non-initial ACL, - * policies, and security labels dumped. - * - * Note that any initial ACLs (see pg_init_privs) will be removed when we - * extract the information about the object. We don't provide support for - * initial policies and security labels and it seems unlikely for those to - * ever exist, but we may have to revisit this later. + * In 9.6 and above, mark the member object to have any non-initial ACLs + * dumped. (Any initial ACLs will be removed later, using data from + * pg_init_privs, so that we'll dump only the delta from the extension's + * initial setup.) * * Prior to 9.6, we do not include any extension member components. * @@ -1500,6 +1497,13 @@ * individually, since the idea is to exactly reproduce the database * contents rather than replace the extension contents with something * different. + * + * Note: it might be interesting someday to implement storage and delta + * dumping of extension members' RLS policies and/or security labels. + * However there is a pitfall for RLS policies: trying to dump them + * requires getting a lock on their tables, and the calling user might not + * have privileges for that. We need no lock to examine a table's ACLs, + * so the current feature doesn't have a problem of that sort. */ if (fout->dopt->binary_upgrade) dobj->dump = ext->dobj.dump; @@ -1508,9 +1512,7 @@ if (fout->remoteVersion < 90600) dobj->dump = DUMP_COMPONENT_NONE; else - dobj->dump = ext->dobj.dump_contains & (DUMP_COMPONENT_ACL | - DUMP_COMPONENT_SECLABEL | - DUMP_COMPONENT_POLICY); + dobj->dump = ext->dobj.dump_contains & (DUMP_COMPONENT_ACL); } return true; @@ -1814,6 +1816,26 @@ } /* + * selectDumpableStatisticsObject: policy-setting subroutine + * Mark an extended statistics object as to be dumped or not + * + * We dump an extended statistics object if the schema it's in and the table + * it's for are being dumped. (This'll need more thought if statistics + * objects ever support cross-table stats.) + */ +static void +selectDumpableStatisticsObject(StatsExtInfo *sobj, Archive *fout) +{ + if (checkExtensionMembership(&sobj->dobj, fout)) + return; /* extension membership overrides all else */ + + sobj->dobj.dump = sobj->dobj.namespace->dobj.dump_contains; + if (sobj->stattable == NULL || + !(sobj->stattable->dobj.dump & DUMP_COMPONENT_DEFINITION)) + sobj->dobj.dump = DUMP_COMPONENT_NONE; +} + +/* * selectDumpableObject: policy-setting subroutine * Mark a generic dumpable object as to be dumped or not * @@ -7490,6 +7512,7 @@ int i_stxname; int i_stxnamespace; int i_rolname; + int i_stxrelid; int i_stattarget; int i; @@ -7501,12 +7524,12 @@ if (fout->remoteVersion < 130000) appendPQExpBuffer(query, "SELECT tableoid, oid, stxname, " - "stxnamespace, (%s stxowner) AS rolname, (-1) AS stxstattarget " + "stxnamespace, (%s stxowner) AS rolname, stxrelid, (-1) AS stxstattarget " "FROM pg_catalog.pg_statistic_ext", username_subquery); else appendPQExpBuffer(query, "SELECT tableoid, oid, stxname, " - "stxnamespace, (%s stxowner) AS rolname, stxstattarget " + "stxnamespace, (%s stxowner) AS rolname, stxrelid, stxstattarget " "FROM pg_catalog.pg_statistic_ext", username_subquery); @@ -7519,6 +7542,7 @@ i_stxname = PQfnumber(res, "stxname"); i_stxnamespace = PQfnumber(res, "stxnamespace"); i_rolname = PQfnumber(res, "rolname"); + i_stxrelid = PQfnumber(res, "stxrelid"); i_stattarget = PQfnumber(res, "stxstattarget"); statsextinfo = (StatsExtInfo *) pg_malloc(ntups * sizeof(StatsExtInfo)); @@ -7534,10 +7558,12 @@ findNamespace(fout, atooid(PQgetvalue(res, i, i_stxnamespace))); statsextinfo[i].rolname = pg_strdup(PQgetvalue(res, i, i_rolname)); + statsextinfo[i].stattable = + findTableByOid(atooid(PQgetvalue(res, i, i_stxrelid))); statsextinfo[i].stattarget = atoi(PQgetvalue(res, i, i_stattarget)); /* Decide whether we want to dump it */ - selectDumpableObject(&(statsextinfo[i].dobj), fout); + selectDumpableStatisticsObject(&(statsextinfo[i]), fout); /* Stats objects do not currently have ACLs. */ statsextinfo[i].dobj.dump &= ~DUMP_COMPONENT_ACL; diff -Nru postgresql-13-13.13/src/bin/pg_dump/pg_dump.h postgresql-13-13.14/src/bin/pg_dump/pg_dump.h --- postgresql-13-13.13/src/bin/pg_dump/pg_dump.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_dump/pg_dump.h 2024-02-05 21:47:02.000000000 +0000 @@ -387,6 +387,7 @@ { DumpableObject dobj; char *rolname; /* name of owner, or empty string */ + TableInfo *stattable; /* link to table the stats are for */ int stattarget; /* statistics target */ } StatsExtInfo; diff -Nru postgresql-13-13.13/src/bin/pg_dump/t/002_pg_dump.pl postgresql-13-13.14/src/bin/pg_dump/t/002_pg_dump.pl --- postgresql-13-13.13/src/bin/pg_dump/t/002_pg_dump.pl 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_dump/t/002_pg_dump.pl 2024-02-05 21:47:02.000000000 +0000 @@ -2751,13 +2751,13 @@ 'CREATE STATISTICS extended_stats_no_options' => { create_order => 97, create_sql => 'CREATE STATISTICS dump_test.test_ext_stats_no_options - ON col1, col2 FROM dump_test.test_fifth_table', + ON col1, col2 FROM dump_test.test_table', regexp => qr/^ - \QCREATE STATISTICS dump_test.test_ext_stats_no_options ON col1, col2 FROM dump_test.test_fifth_table;\E + \QCREATE STATISTICS dump_test.test_ext_stats_no_options ON col1, col2 FROM dump_test.test_table;\E /xms, like => { %full_runs, %dump_test_schema_runs, section_post_data => 1, }, - unlike => { exclude_dump_test_schema => 1, }, + unlike => { exclude_dump_test_schema => 1, exclude_test_table => 1, }, }, 'CREATE STATISTICS extended_stats_options' => { diff -Nru postgresql-13-13.13/src/bin/pg_rewind/t/003_extrafiles.pl postgresql-13-13.14/src/bin/pg_rewind/t/003_extrafiles.pl --- postgresql-13-13.13/src/bin/pg_rewind/t/003_extrafiles.pl 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_rewind/t/003_extrafiles.pl 2024-02-05 21:47:02.000000000 +0000 @@ -67,6 +67,19 @@ }, $test_master_datadir); @paths = sort @paths; + + # File::Find converts backslashes to slashes in the newer Perl + # versions. To support all Perl versions, do the same conversion + # for Windows before comparing the paths. + if ($windows_os) + { + for my $filename (@paths) + { + $filename =~ s{\\}{/}g; + } + $test_master_datadir =~ s{\\}{/}g; + } + is_deeply( \@paths, [ diff -Nru postgresql-13-13.13/src/bin/pg_upgrade/po/uk.po postgresql-13-13.14/src/bin/pg_upgrade/po/uk.po --- postgresql-13-13.13/src/bin/pg_upgrade/po/uk.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_upgrade/po/uk.po 2024-02-05 21:47:02.000000000 +0000 @@ -2,8 +2,8 @@ msgstr "" "Project-Id-Version: postgresql\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" -"POT-Creation-Date: 2022-02-12 18:59+0000\n" -"PO-Revision-Date: 2022-06-19 10:10\n" +"POT-Creation-Date: 2023-12-17 23:00+0000\n" +"PO-Revision-Date: 2023-12-18 17:41\n" "Last-Translator: \n" "Language-Team: Ukrainian\n" "Language: uk_UA\n" @@ -17,28 +17,28 @@ "X-Crowdin-File: /REL_13_STABLE/pg_upgrade.pot\n" "X-Crowdin-File-ID: 510\n" -#: check.c:68 +#: check.c:71 #, c-format msgid "Performing Consistency Checks on Old Live Server\n" "------------------------------------------------\n" msgstr "Перевірка цілістності на старому працюючому сервері\n" "------------------------------------------------\n" -#: check.c:74 +#: check.c:77 #, c-format msgid "Performing Consistency Checks\n" "-----------------------------\n" msgstr "Проведення перевірок цілістності\n" "-----------------------------\n" -#: check.c:195 +#: check.c:208 #, c-format msgid "\n" "*Clusters are compatible*\n" msgstr "\n" "*Кластери сумісні*\n" -#: check.c:201 +#: check.c:214 #, c-format msgid "\n" "If pg_upgrade fails after this point, you must re-initdb the\n" @@ -47,7 +47,7 @@ "Якщо робота pg_upgrade після цієї точки перерветься, вам потрібно буде заново виконати initdb \n" "для нового кластера, перед продовженням.\n" -#: check.c:237 +#: check.c:250 #, c-format msgid "Optimizer statistics are not transferred by pg_upgrade so,\n" "once you start the new server, consider running:\n" @@ -56,14 +56,14 @@ "запустивши новий сервер, має сенс виконати:\n" " %s\n\n" -#: check.c:243 +#: check.c:256 #, c-format msgid "Running this script will delete the old cluster's data files:\n" " %s\n" msgstr "При запуску цього скрипту файли даних старого кластера будуть видалені:\n" " %s\n" -#: check.c:248 +#: check.c:261 #, c-format msgid "Could not create a script to delete the old cluster's data files\n" "because user-defined tablespaces or the new cluster's data directory\n" @@ -74,173 +74,173 @@ "простори або каталог даних нового кластера. Вміст старого кластера\n" "треба буде видалити вручну.\n" -#: check.c:258 +#: check.c:271 #, c-format msgid "Checking cluster versions" msgstr "Перевірка версій кластерів" -#: check.c:270 +#: check.c:283 #, c-format msgid "This utility can only upgrade from PostgreSQL version 8.4 and later.\n" msgstr "Ця утиліта може виконувати оновлення тільки з версії PostgreSQL 8.4 і новіше.\n" -#: check.c:274 +#: check.c:287 #, c-format msgid "This utility can only upgrade to PostgreSQL version %s.\n" msgstr "Ця утиліта може тільки підвищувати версію PostgreSQL до %s.\n" -#: check.c:283 +#: check.c:296 #, c-format msgid "This utility cannot be used to downgrade to older major PostgreSQL versions.\n" msgstr "Ця утиліта не може не може використовуватись щоб понижувати версію до більш старих основних версій PostgreSQL.\n" -#: check.c:288 +#: check.c:301 #, c-format msgid "Old cluster data and binary directories are from different major versions.\n" msgstr "Каталог даних і двійковий каталог старого кластера з різних основних версій.\n" -#: check.c:291 +#: check.c:304 #, c-format msgid "New cluster data and binary directories are from different major versions.\n" msgstr "Каталог даних і двійковий каталог нового кластера з різних основних версій.\n" -#: check.c:308 +#: check.c:321 #, c-format msgid "When checking a pre-PG 9.1 live old server, you must specify the old server's port number.\n" msgstr "Для перевірки старого працюючого сервера до версії 9.1, вам необхідно вказати номер порта цього сервера.\n" -#: check.c:312 +#: check.c:325 #, c-format msgid "When checking a live server, the old and new port numbers must be different.\n" msgstr "Для перевірки працюючого сервера, старий і новий номер порта повинні бути різними.\n" -#: check.c:327 +#: check.c:340 #, c-format msgid "encodings for database \"%s\" do not match: old \"%s\", new \"%s\"\n" msgstr "кодування для бази даних \"%s\" не збігаються: старе \"%s\", нове \"%s\"\n" -#: check.c:332 +#: check.c:345 #, c-format msgid "lc_collate values for database \"%s\" do not match: old \"%s\", new \"%s\"\n" msgstr "значення lc_collate для бази даних \"%s\" не збігаються: старе \"%s\", нове \"%s\"\n" -#: check.c:335 +#: check.c:348 #, c-format msgid "lc_ctype values for database \"%s\" do not match: old \"%s\", new \"%s\"\n" msgstr "значення lc_ctype для бази даних \"%s\" не збігаються: старе \"%s\", нове \"%s\"\n" -#: check.c:408 +#: check.c:421 #, c-format msgid "New cluster database \"%s\" is not empty: found relation \"%s.%s\"\n" msgstr "Новий кластер бази даних \"%s\" не порожній: знайдено відношення \"%s.%s\"\n" -#: check.c:457 +#: check.c:470 #, c-format msgid "Creating script to analyze new cluster" msgstr "Створення скрипту для аналізу нового кластеру" -#: check.c:471 check.c:630 check.c:894 check.c:973 file.c:336 function.c:240 +#: check.c:484 check.c:643 check.c:907 check.c:986 file.c:338 function.c:240 #: option.c:497 version.c:54 version.c:204 version.c:374 version.c:509 #, c-format msgid "could not open file \"%s\": %s\n" msgstr "не вдалося відкрити файл \"%s\": %s\n" -#: check.c:519 check.c:686 +#: check.c:532 check.c:699 #, c-format msgid "could not add execute permission to file \"%s\": %s\n" msgstr "не вдалося додати право виконання для файлу \"%s\": %s\n" -#: check.c:549 +#: check.c:562 #, c-format msgid "Checking for new cluster tablespace directories" msgstr "Перевірка каталогів табличних просторів кластера" -#: check.c:560 +#: check.c:573 #, c-format msgid "new cluster tablespace directory already exists: \"%s\"\n" msgstr "каталог нового кластерного табличного простору вже існує: \"%s\"\n" -#: check.c:593 +#: check.c:606 #, c-format msgid "\n" "WARNING: new data directory should not be inside the old data directory, e.g. %s\n" msgstr "\n" "ПОПЕРЕДЖЕННЯ: новий каталог даних не повинен бути всередині старого каталогу даних, наприклад %s\n" -#: check.c:617 +#: check.c:630 #, c-format msgid "\n" "WARNING: user-defined tablespace locations should not be inside the data directory, e.g. %s\n" msgstr "\n" "ПОПЕРЕДЖЕННЯ: користувацькі розташування табличних просторів не повинні бути всередині каталогу даних, наприклад %s\n" -#: check.c:627 +#: check.c:640 #, c-format msgid "Creating script to delete old cluster" msgstr "Створення скрипту для видалення старого кластеру" -#: check.c:706 +#: check.c:719 #, c-format msgid "Checking database user is the install user" msgstr "Перевірка, чи є користувач бази даних стартовим користувачем" -#: check.c:722 +#: check.c:735 #, c-format msgid "database user \"%s\" is not the install user\n" msgstr "користувач бази даних \"%s\" не є стартовим користувачем\n" -#: check.c:733 +#: check.c:746 #, c-format msgid "could not determine the number of users\n" msgstr "не вдалося визначити кількість користувачів\n" -#: check.c:741 +#: check.c:754 #, c-format msgid "Only the install user can be defined in the new cluster.\n" msgstr "В новому кластері може бути визначеним тільки стартовий користувач.\n" -#: check.c:761 +#: check.c:774 #, c-format msgid "Checking database connection settings" msgstr "Перевірка параметрів підключення до бази даних" -#: check.c:783 +#: check.c:796 #, c-format msgid "template0 must not allow connections, i.e. its pg_database.datallowconn must be false\n" msgstr "template0 не повинна дозволяти підключення, тобто pg_database.datallowconn повинно бути false\n" -#: check.c:793 +#: check.c:806 #, c-format msgid "All non-template0 databases must allow connections, i.e. their pg_database.datallowconn must be true\n" msgstr "Всі бази даних, окрім template0, повинні дозволяти підключення, тобто pg_database.datallowconn повинно бути true\n" -#: check.c:818 +#: check.c:831 #, c-format msgid "Checking for prepared transactions" msgstr "Перевірка підготовлених транзакцій" -#: check.c:827 +#: check.c:840 #, c-format msgid "The source cluster contains prepared transactions\n" msgstr "Початковий кластер містить підготовлені транзакції\n" -#: check.c:829 +#: check.c:842 #, c-format msgid "The target cluster contains prepared transactions\n" msgstr "Цільовий кластер містить підготовлені транзакції\n" -#: check.c:855 +#: check.c:868 #, c-format msgid "Checking for contrib/isn with bigint-passing mismatch" msgstr "Перевірка невідповідності при передаванні bigint в contrib/isn" -#: check.c:916 check.c:995 check.c:1052 check.c:1111 check.c:1140 +#: check.c:929 check.c:1008 check.c:1065 check.c:1124 check.c:1158 check.c:1187 #: function.c:262 version.c:278 version.c:315 version.c:458 #, c-format msgid "fatal\n" msgstr "збій\n" -#: check.c:917 +#: check.c:930 #, c-format msgid "Your installation contains \"contrib/isn\" functions which rely on the\n" "bigint data type. Your old and new clusters pass bigint values\n" @@ -252,12 +252,12 @@ msgstr "Ваша інсталяція містить функції \"contrib/isn\", що використовують тип даних bigint. Старі та нові кластери передають значення bigint по-різному, тому цей кластер наразі неможливо оновити. Ви можете вручну вивантажити бази даних зі старого кластеру, що використовує засоби \"contrib/isn\", видалити їх, виконати оновлення, а потім відновити їх. Список проблемних функцій подано у файлі:\n" " %s\n\n" -#: check.c:941 +#: check.c:954 #, c-format msgid "Checking for tables WITH OIDS" msgstr "Перевірка таблиць WITH OIDS" -#: check.c:996 +#: check.c:1009 #, c-format msgid "Your installation contains tables declared WITH OIDS, which is not\n" "supported anymore. Consider removing the oid column using\n" @@ -269,12 +269,12 @@ "Список проблемних таблиць подано у файлі:\n" " %s\n\n" -#: check.c:1024 +#: check.c:1037 #, c-format msgid "Checking for system-defined composite types in user tables" msgstr "Перевірка складених типів визначених системою у таблицях користувача" -#: check.c:1053 +#: check.c:1066 #, c-format msgid "Your installation contains system-defined composite type(s) in user tables.\n" "These type OIDs are not stable across PostgreSQL versions,\n" @@ -288,12 +288,12 @@ "Список проблемних стовпців знаходиться у файлі:\n" " %s\n\n" -#: check.c:1081 +#: check.c:1094 #, c-format msgid "Checking for reg* data types in user tables" msgstr "Перевірка типів даних reg* в користувацьких таблицях" -#: check.c:1112 +#: check.c:1125 #, c-format msgid "Your installation contains one of the reg* data types in user tables.\n" "These data types reference system OIDs that are not preserved by\n" @@ -304,12 +304,32 @@ msgstr "Користувацькі таблиці у вашій інсталяції містять один з типів даних reg*. Ці типи даних посилаються на системні OIDs, що не зберігаються за допомогою pg_upgrade, тому цей кластер наразі неможливо оновити. Ви можете видалити проблемні таблиці і перезавантажити оновлення. Список проблемних стовпців подано у файлі:\n" " %s\n\n" -#: check.c:1134 +#: check.c:1149 +#, c-format +msgid "Checking for removed \"%s\" data type in user tables" +msgstr "Перевірка видаленого типу даних \"%s\" в користувацьких таблицях" + +#: check.c:1159 +#, c-format +msgid "Your installation contains the \"%s\" data type in user tables.\n" +"The \"%s\" type has been removed in PostgreSQL version %s,\n" +"so this cluster cannot currently be upgraded. You can drop the\n" +"problem columns, or change them to another data type, and restart\n" +"the upgrade. A list of the problem columns is in the file:\n" +" %s\n\n" +msgstr "Користувацькі таблиці у вашій інсталяції містять тип даних \"%s\".\n" +"Тип \"%s\" був видалений з версії PostgreSQL %s, тому цей кластер \n" +"наразі не може бути оновлений. Ви можете видалите проблемні \n" +"стовпці або змінити їх на інший тип даних, і перезапустити\n" +"оновлення. Список проблемних стовпців є у файлі:\n" +" %s\n\n" + +#: check.c:1181 #, c-format msgid "Checking for incompatible \"jsonb\" data type" msgstr "Перевірка несумісного типу даних \"jsonb\"" -#: check.c:1141 +#: check.c:1188 #, c-format msgid "Your installation contains the \"jsonb\" data type in user tables.\n" "The internal format of \"jsonb\" changed during 9.4 beta so this\n" @@ -320,32 +340,32 @@ msgstr "Користувацькі таблиці у вашій інсталяції містять тип даних \"jsonb\". Внутрішній формат \"jsonb\" змінено під час версії 9.4 beta, тому цей кластер наразі неможливо оновити. Ви можете видалити проблемні таблиці та перезавантажити оновлення. Список проблемних таблиць подано у файлі:\n" " %s\n\n" -#: check.c:1163 +#: check.c:1210 #, c-format msgid "Checking for roles starting with \"pg_\"" msgstr "Перевірка ролей, які починаються з \"pg_\"" -#: check.c:1173 +#: check.c:1220 #, c-format msgid "The source cluster contains roles starting with \"pg_\"\n" msgstr "Початковий кластер містить ролі, які починаються з \"pg_\"\n" -#: check.c:1175 +#: check.c:1222 #, c-format msgid "The target cluster contains roles starting with \"pg_\"\n" msgstr "Цільовий кластер містить ролі, які починаються з \"pg_\"\n" -#: check.c:1201 +#: check.c:1248 #, c-format msgid "failed to get the current locale\n" msgstr "не вдалося отримати поточну локаль\n" -#: check.c:1210 +#: check.c:1257 #, c-format msgid "failed to get system locale name for \"%s\"\n" msgstr "не вдалося отримати системне ім'я локалі для \"%s\"\n" -#: check.c:1216 +#: check.c:1263 #, c-format msgid "failed to restore old locale \"%s\"\n" msgstr "не вдалося відновити стару локаль \"%s\"\n" @@ -412,194 +432,194 @@ msgid "%d: controldata retrieval problem\n" msgstr "%d: проблема з отриманням контрольних даних\n" -#: controldata.c:558 +#: controldata.c:557 #, c-format msgid "The source cluster lacks some required control information:\n" msgstr "У початковому кластері відсутня необхідна контрольна інформація:\n" -#: controldata.c:561 +#: controldata.c:560 #, c-format msgid "The target cluster lacks some required control information:\n" msgstr "У цільовому кластері відсутня необхідна контрольна інформація:\n" -#: controldata.c:564 +#: controldata.c:563 #, c-format msgid " checkpoint next XID\n" msgstr " наступний XID контрольної точки\n" -#: controldata.c:567 +#: controldata.c:566 #, c-format msgid " latest checkpoint next OID\n" msgstr " наступний OID останньої контрольної точки\n" -#: controldata.c:570 +#: controldata.c:569 #, c-format msgid " latest checkpoint next MultiXactId\n" msgstr " наступний MultiXactId останньої контрольної точки\n" -#: controldata.c:574 +#: controldata.c:573 #, c-format msgid " latest checkpoint oldest MultiXactId\n" msgstr " найстарший MultiXactId останньої контрольної точки\n" -#: controldata.c:577 +#: controldata.c:576 #, c-format msgid " latest checkpoint oldestXID\n" msgstr " найстарший oldestXID останньої контрольної точки\n" -#: controldata.c:580 +#: controldata.c:579 #, c-format msgid " latest checkpoint next MultiXactOffset\n" msgstr " наступний MultiXactOffset останньої контрольної точки\n" -#: controldata.c:583 +#: controldata.c:582 #, c-format msgid " first WAL segment after reset\n" msgstr " перший сегмет WAL після скидання\n" -#: controldata.c:586 +#: controldata.c:585 #, c-format msgid " float8 argument passing method\n" msgstr " метод передачі аргументу float8\n" -#: controldata.c:589 +#: controldata.c:588 #, c-format msgid " maximum alignment\n" msgstr " максимальне вирівнювання\n" -#: controldata.c:592 +#: controldata.c:591 #, c-format msgid " block size\n" msgstr " розмір блоку\n" -#: controldata.c:595 +#: controldata.c:594 #, c-format msgid " large relation segment size\n" msgstr " розмір сегменту великого відношення\n" -#: controldata.c:598 +#: controldata.c:597 #, c-format msgid " WAL block size\n" msgstr " розмір блоку WAL\n" -#: controldata.c:601 +#: controldata.c:600 #, c-format msgid " WAL segment size\n" msgstr " розмір сегменту WAL\n" -#: controldata.c:604 +#: controldata.c:603 #, c-format msgid " maximum identifier length\n" msgstr " максимальна довжина ідентифікатора\n" -#: controldata.c:607 +#: controldata.c:606 #, c-format msgid " maximum number of indexed columns\n" msgstr " максимальна кількість індексованих стовпців\n" -#: controldata.c:610 +#: controldata.c:609 #, c-format msgid " maximum TOAST chunk size\n" msgstr " максимальний розмір порції TOAST\n" -#: controldata.c:614 +#: controldata.c:613 #, c-format msgid " large-object chunk size\n" msgstr " розмір порції великого об'єкту\n" -#: controldata.c:617 +#: controldata.c:616 #, c-format msgid " dates/times are integers?\n" msgstr " дата/час представлені цілими числами?\n" -#: controldata.c:621 +#: controldata.c:620 #, c-format msgid " data checksum version\n" msgstr " версія контрольних сум даних\n" -#: controldata.c:623 +#: controldata.c:622 #, c-format msgid "Cannot continue without required control information, terminating\n" msgstr "Не можна продовжити без необхідної контрольної інформації, завершення\n" -#: controldata.c:638 +#: controldata.c:637 #, c-format msgid "old and new pg_controldata alignments are invalid or do not match\n" "Likely one cluster is a 32-bit install, the other 64-bit\n" msgstr "старе і нове вирівнювання в pg_controldata неприпустимі або не збігаються\n" "Ймовірно, один кластер встановлений у 32-бітній системі, а інший - у 64-бітній\n" -#: controldata.c:642 +#: controldata.c:641 #, c-format msgid "old and new pg_controldata block sizes are invalid or do not match\n" msgstr "старий і новий розмір блоків в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:645 +#: controldata.c:644 #, c-format msgid "old and new pg_controldata maximum relation segment sizes are invalid or do not match\n" msgstr "старий і новий максимальний розмір сегментів відношень в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:648 +#: controldata.c:647 #, c-format msgid "old and new pg_controldata WAL block sizes are invalid or do not match\n" msgstr "старий і новий розмір блоків WAL в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:651 +#: controldata.c:650 #, c-format msgid "old and new pg_controldata WAL segment sizes are invalid or do not match\n" msgstr "старий і новий розмір сегментів WAL в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:654 +#: controldata.c:653 #, c-format msgid "old and new pg_controldata maximum identifier lengths are invalid or do not match\n" msgstr "стара і нова максимальна довжина ідентифікаторів в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:657 +#: controldata.c:656 #, c-format msgid "old and new pg_controldata maximum indexed columns are invalid or do not match\n" msgstr "стара і нова максимальна кількість індексованих стовпців в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:660 +#: controldata.c:659 #, c-format msgid "old and new pg_controldata maximum TOAST chunk sizes are invalid or do not match\n" msgstr "старий і новий максимальний розмір порції TOAST в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:665 +#: controldata.c:664 #, c-format msgid "old and new pg_controldata large-object chunk sizes are invalid or do not match\n" msgstr "старий і новий розмір порції великого об'єкту в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:668 +#: controldata.c:667 #, c-format msgid "old and new pg_controldata date/time storage types do not match\n" msgstr "старий і новий тип сховища дати/часу в pg_controldata неприпустимі або не збігаються\n" -#: controldata.c:681 +#: controldata.c:680 #, c-format msgid "old cluster does not use data checksums but the new one does\n" msgstr "старий кластер не використовує контрольні суми даних, але новий використовує\n" -#: controldata.c:684 +#: controldata.c:683 #, c-format msgid "old cluster uses data checksums but the new one does not\n" msgstr "старий кластер використовує контрольні суми даних, але новий не використовує\n" -#: controldata.c:686 +#: controldata.c:685 #, c-format msgid "old and new cluster pg_controldata checksum versions do not match\n" msgstr "стара і нова версія контрольних сум кластера в pg_controldata не збігаються\n" -#: controldata.c:697 +#: controldata.c:696 #, c-format msgid "Adding \".old\" suffix to old global/pg_control" msgstr "Додавання суфікса \".old\" до старого файла global/pg_control" -#: controldata.c:702 +#: controldata.c:701 #, c-format msgid "Unable to rename %s to %s.\n" msgstr "Не вдалося перейменувати %s на %s.\n" -#: controldata.c:705 +#: controldata.c:704 #, c-format msgid "\n" "If you want to start the old cluster, you will need to remove\n" @@ -713,7 +733,7 @@ msgid "check for \"%s\" failed: cannot execute (permission denied)\n" msgstr "перевірка \"%s\" провалена: виконання неможливе (немає доступу)\n" -#: file.c:43 file.c:61 +#: file.c:43 file.c:63 #, c-format msgid "error while cloning relation \"%s.%s\" (\"%s\" to \"%s\"): %s\n" msgstr "помилка при клонуванні відношення \"%s.%s\" (\"%s\" до \"%s\"): %s\n" @@ -728,62 +748,62 @@ msgid "error while cloning relation \"%s.%s\": could not create file \"%s\": %s\n" msgstr "помилка при клонуванні відношення \"%s.%s\": не вдалося створити файл \"%s\": %s\n" -#: file.c:87 file.c:190 +#: file.c:89 file.c:192 #, c-format msgid "error while copying relation \"%s.%s\": could not open file \"%s\": %s\n" msgstr "помилка під час копіювання відношення \"%s.%s\": не вдалося відкрити файл \"%s\": %s\n" -#: file.c:92 file.c:199 +#: file.c:94 file.c:201 #, c-format msgid "error while copying relation \"%s.%s\": could not create file \"%s\": %s\n" msgstr "помилка під час копіювання відношення \"%s.%s\": не вдалося створити файл \"%s\": %s\n" -#: file.c:106 file.c:223 +#: file.c:108 file.c:225 #, c-format msgid "error while copying relation \"%s.%s\": could not read file \"%s\": %s\n" msgstr "помилка під час копіювання відношення \"%s.%s\": не вдалося прочитати файл \"%s\": %s\n" -#: file.c:118 file.c:301 +#: file.c:120 file.c:303 #, c-format msgid "error while copying relation \"%s.%s\": could not write file \"%s\": %s\n" msgstr "помилка під час копіювання відношення \"%s.%s\": не вдалося записати до файлу \"%s\": %s\n" -#: file.c:132 +#: file.c:134 #, c-format msgid "error while copying relation \"%s.%s\" (\"%s\" to \"%s\"): %s\n" msgstr "помилка під час копіювання відношення \"%s.%s\" ( з \"%s\" в \"%s\"): %s\n" -#: file.c:151 +#: file.c:153 #, c-format msgid "error while creating link for relation \"%s.%s\" (\"%s\" to \"%s\"): %s\n" msgstr "помилка під час створення посилання для відношення \"%s.%s\" ( з \"%s\" в \"%s\"): %s\n" -#: file.c:194 +#: file.c:196 #, c-format msgid "error while copying relation \"%s.%s\": could not stat file \"%s\": %s\n" msgstr "помилка під час копіювання відношення \"%s.%s\": не вдалося отримати стан файлу \"%s\": %s\n" -#: file.c:226 +#: file.c:228 #, c-format msgid "error while copying relation \"%s.%s\": partial page found in file \"%s\"\n" msgstr "помилка під час копіювання відношення \"%s.%s\": у файлі \"%s\" знайдена часткова сторінка\n" -#: file.c:328 file.c:345 +#: file.c:330 file.c:347 #, c-format msgid "could not clone file between old and new data directories: %s\n" msgstr "не вдалося клонувати файл між старим і новим каталогами даних: %s\n" -#: file.c:341 +#: file.c:343 #, c-format msgid "could not create file \"%s\": %s\n" msgstr "не можливо створити файл \"%s\": %s\n" -#: file.c:352 +#: file.c:354 #, c-format msgid "file cloning not supported on this platform\n" msgstr "клонування файлів не підтримується на цій платформі\n" -#: file.c:369 +#: file.c:371 #, c-format msgid "could not create hard link between old and new data directories: %s\n" "In link mode the old and new data directories must be on the same file system.\n" @@ -906,7 +926,7 @@ msgid "%s.%s: %u to %u\n" msgstr "%s.%s: %u в %u\n" -#: info.c:297 info.c:633 +#: info.c:297 info.c:632 #, c-format msgid "\n\n" msgstr "\n\n" @@ -925,12 +945,12 @@ msgstr "\n" "цільові бази даних:\n" -#: info.c:631 +#: info.c:630 #, c-format msgid "Database: %s\n" msgstr "База даних: %s\n" -#: info.c:644 +#: info.c:643 #, c-format msgid "relname: %s.%s: reloid: %u reltblspace: %s\n" msgstr "ім'я_відношення: %s.%s: oid_відношення: %u табл_простір: %s\n" diff -Nru postgresql-13-13.13/src/bin/pg_waldump/po/de.po postgresql-13-13.14/src/bin/pg_waldump/po/de.po --- postgresql-13-13.13/src/bin/pg_waldump/po/de.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/pg_waldump/po/de.po 2024-02-05 21:47:02.000000000 +0000 @@ -8,7 +8,7 @@ "Project-Id-Version: pg_waldump (PostgreSQL) 13\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" "POT-Creation-Date: 2022-11-03 20:43+0000\n" -"PO-Revision-Date: 2020-04-21 19:02+0200\n" +"PO-Revision-Date: 2023-11-08 21:54+0100\n" "Last-Translator: Peter Eisentraut \n" "Language-Team: German \n" "Language: de\n" @@ -222,7 +222,7 @@ #: pg_waldump.c:885 #, c-format msgid "resource manager \"%s\" does not exist" -msgstr "Resouce-Manager »%s« existiert nicht" +msgstr "Resource-Manager »%s« existiert nicht" #: pg_waldump.c:894 #, c-format diff -Nru postgresql-13-13.13/src/bin/psql/po/ja.po postgresql-13-13.14/src/bin/psql/po/ja.po --- postgresql-13-13.13/src/bin/psql/po/ja.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/psql/po/ja.po 2024-02-05 21:47:02.000000000 +0000 @@ -8,7 +8,7 @@ "Project-Id-Version: psql (PostgreSQL 13)\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" "POT-Creation-Date: 2023-02-06 15:57+0900\n" -"PO-Revision-Date: 2023-02-06 17:39+0900\n" +"PO-Revision-Date: 2023-11-22 10:49+0900\n" "Last-Translator: Kyotaro Horiguchi \n" "Language-Team: Japan PostgreSQL Users Group \n" "Language: ja\n" @@ -152,7 +152,7 @@ #: ../../fe_utils/print.c:3120 #, c-format msgid "Cannot add header to table content: column count of %d exceeded.\n" -msgstr "テーブルの内容にヘッダーを追加できません: 列数 %d が制限値を超えています。\n" +msgstr "テーブルの内容にヘッダーを追加できません: 列数の上限値 %d を超えています。\n" #: ../../fe_utils/print.c:3160 #, c-format diff -Nru postgresql-13-13.13/src/bin/scripts/po/uk.po postgresql-13-13.14/src/bin/scripts/po/uk.po --- postgresql-13-13.13/src/bin/scripts/po/uk.po 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/bin/scripts/po/uk.po 2024-02-05 21:47:02.000000000 +0000 @@ -2,8 +2,8 @@ msgstr "" "Project-Id-Version: postgresql\n" "Report-Msgid-Bugs-To: pgsql-bugs@lists.postgresql.org\n" -"POT-Creation-Date: 2022-03-16 09:30+0000\n" -"PO-Revision-Date: 2022-06-19 10:10\n" +"POT-Creation-Date: 2023-12-17 23:01+0000\n" +"PO-Revision-Date: 2023-12-18 17:41\n" "Last-Translator: \n" "Language-Team: Ukrainian\n" "Language: uk_UA\n" @@ -128,134 +128,134 @@ msgid "clustering of database \"%s\" failed: %s" msgstr "кластеризувати базу даних \"%s\" не вдалося: %s" -#: clusterdb.c:249 +#: clusterdb.c:251 #, c-format msgid "%s: clustering database \"%s\"\n" msgstr "%s: кластеризація бази даних \"%s\"\n" -#: clusterdb.c:265 +#: clusterdb.c:267 #, c-format msgid "%s clusters all previously clustered tables in a database.\n\n" msgstr "%s кластеризація усіх попередньо кластеризованих таблиць в базі даних.\n\n" -#: clusterdb.c:266 createdb.c:266 createuser.c:354 dropdb.c:170 dropuser.c:170 -#: pg_isready.c:224 reindexdb.c:750 vacuumdb.c:911 +#: clusterdb.c:268 createdb.c:266 createuser.c:354 dropdb.c:170 dropuser.c:170 +#: pg_isready.c:224 reindexdb.c:752 vacuumdb.c:911 #, c-format msgid "Usage:\n" msgstr "Використання:\n" -#: clusterdb.c:267 reindexdb.c:751 vacuumdb.c:912 +#: clusterdb.c:269 reindexdb.c:753 vacuumdb.c:912 #, c-format msgid " %s [OPTION]... [DBNAME]\n" msgstr " %s [OPTION]... [DBNAME]\n" -#: clusterdb.c:268 createdb.c:268 createuser.c:356 dropdb.c:172 dropuser.c:172 -#: pg_isready.c:227 reindexdb.c:752 vacuumdb.c:913 +#: clusterdb.c:270 createdb.c:268 createuser.c:356 dropdb.c:172 dropuser.c:172 +#: pg_isready.c:227 reindexdb.c:754 vacuumdb.c:913 #, c-format msgid "\n" "Options:\n" msgstr "\n" "Параметри:\n" -#: clusterdb.c:269 +#: clusterdb.c:271 #, c-format msgid " -a, --all cluster all databases\n" msgstr " -a, --all кластеризація усіх баз даних\n" -#: clusterdb.c:270 +#: clusterdb.c:272 #, c-format msgid " -d, --dbname=DBNAME database to cluster\n" msgstr " -d, --dbname=ІМ'Я_БД база даних для кластеризації\n" -#: clusterdb.c:271 createuser.c:360 dropdb.c:173 dropuser.c:173 reindexdb.c:756 +#: clusterdb.c:273 createuser.c:360 dropdb.c:173 dropuser.c:173 reindexdb.c:758 #, c-format msgid " -e, --echo show the commands being sent to the server\n" msgstr " -e, --echo показати команди, надіслані серверу\n" -#: clusterdb.c:272 reindexdb.c:759 +#: clusterdb.c:274 reindexdb.c:761 #, c-format msgid " -q, --quiet don't write any messages\n" msgstr " -q, --quiet не виводити жодних повідомлень\n" -#: clusterdb.c:273 +#: clusterdb.c:275 #, c-format msgid " -t, --table=TABLE cluster specific table(s) only\n" msgstr " -t, --table=ТАБЛИЦЯ кластеризувати тільки вказані таблиці\n" -#: clusterdb.c:274 reindexdb.c:763 +#: clusterdb.c:276 reindexdb.c:765 #, c-format msgid " -v, --verbose write a lot of output\n" msgstr " -v, --verbose виводити багато інформації\n" -#: clusterdb.c:275 createuser.c:372 dropdb.c:176 dropuser.c:176 reindexdb.c:764 +#: clusterdb.c:277 createuser.c:372 dropdb.c:176 dropuser.c:176 reindexdb.c:766 #, c-format msgid " -V, --version output version information, then exit\n" msgstr " -V, --version вивести інформацію про версію і вийти\n" -#: clusterdb.c:276 createuser.c:377 dropdb.c:178 dropuser.c:178 reindexdb.c:765 +#: clusterdb.c:278 createuser.c:377 dropdb.c:178 dropuser.c:178 reindexdb.c:767 #, c-format msgid " -?, --help show this help, then exit\n" msgstr " -?, --help показати цю довідку, потім вийти\n" -#: clusterdb.c:277 createdb.c:279 createuser.c:378 dropdb.c:179 dropuser.c:179 -#: pg_isready.c:233 reindexdb.c:766 vacuumdb.c:934 +#: clusterdb.c:279 createdb.c:279 createuser.c:378 dropdb.c:179 dropuser.c:179 +#: pg_isready.c:233 reindexdb.c:768 vacuumdb.c:934 #, c-format msgid "\n" "Connection options:\n" msgstr "\n" "Налаштування з'єднання:\n" -#: clusterdb.c:278 createuser.c:379 dropdb.c:180 dropuser.c:180 reindexdb.c:767 +#: clusterdb.c:280 createuser.c:379 dropdb.c:180 dropuser.c:180 reindexdb.c:769 #: vacuumdb.c:935 #, c-format msgid " -h, --host=HOSTNAME database server host or socket directory\n" msgstr " -h, --host=HOSTNAME хост сервера бази даних або каталог сокетів\n" -#: clusterdb.c:279 createuser.c:380 dropdb.c:181 dropuser.c:181 reindexdb.c:768 +#: clusterdb.c:281 createuser.c:380 dropdb.c:181 dropuser.c:181 reindexdb.c:770 #: vacuumdb.c:936 #, c-format msgid " -p, --port=PORT database server port\n" msgstr " -p, --port=PORT порт сервера бази даних\n" -#: clusterdb.c:280 dropdb.c:182 reindexdb.c:769 vacuumdb.c:937 +#: clusterdb.c:282 dropdb.c:182 reindexdb.c:771 vacuumdb.c:937 #, c-format msgid " -U, --username=USERNAME user name to connect as\n" msgstr " -U, --username=ІМ'Я_КОРИСТУВАЧА ім'я користувача для з'єднання з сервером\n" -#: clusterdb.c:281 createuser.c:382 dropdb.c:183 dropuser.c:183 reindexdb.c:770 +#: clusterdb.c:283 createuser.c:382 dropdb.c:183 dropuser.c:183 reindexdb.c:772 #: vacuumdb.c:938 #, c-format msgid " -w, --no-password never prompt for password\n" msgstr " -w, --no-password ніколи не запитувати пароль\n" -#: clusterdb.c:282 createuser.c:383 dropdb.c:184 dropuser.c:184 reindexdb.c:771 +#: clusterdb.c:284 createuser.c:383 dropdb.c:184 dropuser.c:184 reindexdb.c:773 #: vacuumdb.c:939 #, c-format msgid " -W, --password force password prompt\n" msgstr " -W, --password запросити пароль\n" -#: clusterdb.c:283 dropdb.c:185 reindexdb.c:772 vacuumdb.c:940 +#: clusterdb.c:285 dropdb.c:185 reindexdb.c:774 vacuumdb.c:940 #, c-format msgid " --maintenance-db=DBNAME alternate maintenance database\n" msgstr " --maintenance-db=DBNAME альтернативна бази даних для обслуговування\n" -#: clusterdb.c:284 +#: clusterdb.c:286 #, c-format msgid "\n" "Read the description of the SQL command CLUSTER for details.\n" msgstr "\n" "Для деталей читайте опис команди SQL CLUSTER.\n" -#: clusterdb.c:285 createdb.c:287 createuser.c:384 dropdb.c:186 dropuser.c:185 -#: pg_isready.c:238 reindexdb.c:774 vacuumdb.c:942 +#: clusterdb.c:287 createdb.c:287 createuser.c:384 dropdb.c:186 dropuser.c:185 +#: pg_isready.c:238 reindexdb.c:776 vacuumdb.c:942 #, c-format msgid "\n" "Report bugs to <%s>.\n" msgstr "\n" "Повідомляти про помилки на <%s>.\n" -#: clusterdb.c:286 createdb.c:288 createuser.c:385 dropdb.c:187 dropuser.c:186 -#: pg_isready.c:239 reindexdb.c:775 vacuumdb.c:943 +#: clusterdb.c:288 createdb.c:288 createuser.c:385 dropdb.c:187 dropuser.c:186 +#: pg_isready.c:239 reindexdb.c:777 vacuumdb.c:943 #, c-format msgid "%s home page: <%s>\n" msgstr "Домашня сторінка %s: <%s>\n" @@ -845,67 +845,72 @@ msgid "reindexing of table \"%s\" in database \"%s\" failed: %s" msgstr "переіндексувати таблиці \"%s\" в базі даних \"%s\" не вдалося: %s" -#: reindexdb.c:732 +#: reindexdb.c:734 #, c-format msgid "%s: reindexing database \"%s\"\n" msgstr "%s: переіндексування бази даних \"%s\"\n" -#: reindexdb.c:749 +#: reindexdb.c:751 #, c-format msgid "%s reindexes a PostgreSQL database.\n\n" msgstr "%s переіндексовує базу даних PostgreSQL.\n\n" -#: reindexdb.c:753 +#: reindexdb.c:755 #, c-format msgid " -a, --all reindex all databases\n" msgstr " -a, --all переіндексувати усі бази даних\n" -#: reindexdb.c:754 +#: reindexdb.c:756 #, c-format msgid " --concurrently reindex concurrently\n" msgstr " --concurrently переіндексувати одночасно\n" -#: reindexdb.c:755 +#: reindexdb.c:757 #, c-format msgid " -d, --dbname=DBNAME database to reindex\n" msgstr " -d, --dbname=ІМ'Я_БД база даних для переіндексування\n" -#: reindexdb.c:757 +#: reindexdb.c:759 #, c-format msgid " -i, --index=INDEX recreate specific index(es) only\n" msgstr " -i, --index=ІНДЕКС відтворити тільки вказані індекси\n" -#: reindexdb.c:758 +#: reindexdb.c:760 #, c-format msgid " -j, --jobs=NUM use this many concurrent connections to reindex\n" msgstr " -j, --jobs=NUM використати таку кількість паралельних підключень для переіндексації\n" -#: reindexdb.c:760 +#: reindexdb.c:762 #, c-format msgid " -s, --system reindex system catalogs only\n" msgstr " -s, --system переіндексувати тільки системні каталоги\n" -#: reindexdb.c:761 +#: reindexdb.c:763 #, c-format msgid " -S, --schema=SCHEMA reindex specific schema(s) only\n" msgstr " -S, --schema=СХЕМА переіндексувати тільки вказані схеми\n" -#: reindexdb.c:762 +#: reindexdb.c:764 #, c-format msgid " -t, --table=TABLE reindex specific table(s) only\n" msgstr " -t, --table=ТАБЛИЦЯ переіндексувати тільки вказані таблиці\n" -#: reindexdb.c:773 +#: reindexdb.c:775 #, c-format msgid "\n" "Read the description of the SQL command REINDEX for details.\n" msgstr "\n" "Для деталей читайте опис команди SQL REINDEX.\n" -#: scripts_parallel.c:232 +#: scripts_parallel.c:244 +#, c-format +msgid "too many jobs for this platform: %d" +msgstr "занадто багато завдань для цієї платформи: %d" + +#: scripts_parallel.c:253 #, c-format -msgid "too many jobs for this platform -- try %d" -msgstr "надто багато завдань для цієї платформи -- спробуйте %d" +msgid "socket file descriptor out of range for select(): %d" +msgstr "дескриптор файлу сокету поза діапазоном для select(): %d" #: vacuumdb.c:192 #, c-format diff -Nru postgresql-13-13.13/src/include/access/tableam.h postgresql-13-13.14/src/include/access/tableam.h --- postgresql-13-13.13/src/include/access/tableam.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/access/tableam.h 2024-02-05 21:47:02.000000000 +0000 @@ -1235,8 +1235,8 @@ * TM_BeingModified (the last only possible if wait == false). * * In the failure cases, the routine fills *tmfd with the tuple's t_ctid, - * t_xmax, and, if possible, and, if possible, t_cmax. See comments for - * struct TM_FailureData for additional info. + * t_xmax, and, if possible, t_cmax. See comments for struct + * TM_FailureData for additional info. */ static inline TM_Result table_tuple_delete(Relation rel, ItemPointer tid, CommandId cid, diff -Nru postgresql-13-13.13/src/include/common/int.h postgresql-13-13.14/src/include/common/int.h --- postgresql-13-13.13/src/include/common/int.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/common/int.h 2024-02-05 21:47:02.000000000 +0000 @@ -200,8 +200,12 @@ *result = (int64) res; return false; #else + /* + * Note: overflow is also possible when a == 0 and b < 0 (specifically, + * when b == PG_INT64_MIN). + */ if ((a < 0 && b > 0 && a < PG_INT64_MIN + b) || - (a > 0 && b < 0 && a > PG_INT64_MAX + b)) + (a >= 0 && b < 0 && a > PG_INT64_MAX + b)) { *result = 0x5EED; /* to avoid spurious warnings */ return true; diff -Nru postgresql-13-13.13/src/include/jit/llvmjit.h postgresql-13-13.14/src/include/jit/llvmjit.h --- postgresql-13-13.13/src/include/jit/llvmjit.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/jit/llvmjit.h 2024-02-05 21:47:02.000000000 +0000 @@ -42,6 +42,13 @@ /* number of modules created */ size_t module_generation; + /* + * The LLVM Context used by this JIT context. An LLVM context is reused + * across many compilations, but occasionally reset to prevent it using + * too much memory due to more and more types accumulating. + */ + LLVMContextRef llvm_context; + /* current, "open for write", module */ LLVMModuleRef module; @@ -105,6 +112,7 @@ LLVMModuleRef mod, FunctionCallInfo fcinfo); +extern void llvm_inline_reset_caches(void); extern void llvm_inline(LLVMModuleRef mod); /* diff -Nru postgresql-13-13.13/src/include/jit/llvmjit_emit.h postgresql-13-13.14/src/include/jit/llvmjit_emit.h --- postgresql-13-13.13/src/include/jit/llvmjit_emit.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/jit/llvmjit_emit.h 2024-02-05 21:47:02.000000000 +0000 @@ -45,36 +45,36 @@ * Emit constant integer. */ static inline LLVMValueRef -l_int8_const(int8 i) +l_int8_const(LLVMContextRef lc, int8 i) { - return LLVMConstInt(LLVMInt8Type(), i, false); + return LLVMConstInt(LLVMInt8TypeInContext(lc), i, false); } /* * Emit constant integer. */ static inline LLVMValueRef -l_int16_const(int16 i) +l_int16_const(LLVMContextRef lc, int16 i) { - return LLVMConstInt(LLVMInt16Type(), i, false); + return LLVMConstInt(LLVMInt16TypeInContext(lc), i, false); } /* * Emit constant integer. */ static inline LLVMValueRef -l_int32_const(int32 i) +l_int32_const(LLVMContextRef lc, int32 i) { - return LLVMConstInt(LLVMInt32Type(), i, false); + return LLVMConstInt(LLVMInt32TypeInContext(lc), i, false); } /* * Emit constant integer. */ static inline LLVMValueRef -l_int64_const(int64 i) +l_int64_const(LLVMContextRef lc, int64 i) { - return LLVMConstInt(LLVMInt64Type(), i, false); + return LLVMConstInt(LLVMInt64TypeInContext(lc), i, false); } /* @@ -177,12 +177,15 @@ { char buf[512]; va_list args; + LLVMContextRef lc; va_start(args, fmt); vsnprintf(buf, sizeof(buf), fmt, args); va_end(args); - return LLVMInsertBasicBlock(r, buf); + lc = LLVMGetTypeContext(LLVMTypeOf(LLVMGetBasicBlockParent(r))); + + return LLVMInsertBasicBlockInContext(lc, r, buf); } /* separate, because pg_attribute_printf(2, 3) can't appear in definition */ @@ -197,12 +200,15 @@ { char buf[512]; va_list args; + LLVMContextRef lc; va_start(args, fmt); vsnprintf(buf, sizeof(buf), fmt, args); va_end(args); - return LLVMAppendBasicBlock(f, buf); + lc = LLVMGetTypeContext(LLVMTypeOf(f)); + + return LLVMAppendBasicBlockInContext(lc, f, buf); } /* @@ -214,7 +220,7 @@ const char argname[] = "readonly"; LLVMAttributeRef ref; - ref = LLVMCreateStringAttribute(LLVMGetGlobalContext(), + ref = LLVMCreateStringAttribute(LLVMGetTypeContext(LLVMTypeOf(f)), argname, sizeof(argname) - 1, NULL, 0); @@ -234,7 +240,7 @@ id = LLVMGetEnumAttributeKindForName(argname, sizeof(argname) - 1); - attr = LLVMCreateEnumAttribute(LLVMGetGlobalContext(), id, 0); + attr = LLVMCreateEnumAttribute(LLVMGetTypeContext(LLVMTypeOf(f)), id, 0); LLVMAddCallSiteAttribute(f, LLVMAttributeFunctionIndex, attr); } diff -Nru postgresql-13-13.13/src/include/optimizer/optimizer.h postgresql-13-13.14/src/include/optimizer/optimizer.h --- postgresql-13-13.13/src/include/optimizer/optimizer.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/optimizer/optimizer.h 2024-02-05 21:47:02.000000000 +0000 @@ -131,7 +131,9 @@ /* in util/clauses.c: */ extern bool contain_mutable_functions(Node *clause); +extern bool contain_mutable_functions_after_planning(Expr *expr); extern bool contain_volatile_functions(Node *clause); +extern bool contain_volatile_functions_after_planning(Expr *expr); extern bool contain_volatile_functions_not_nextval(Node *clause); extern Node *eval_const_expressions(PlannerInfo *root, Node *node); diff -Nru postgresql-13-13.13/src/include/pg_config.h.in postgresql-13-13.14/src/include/pg_config.h.in --- postgresql-13-13.13/src/include/pg_config.h.in 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/pg_config.h.in 2024-02-05 21:47:02.000000000 +0000 @@ -86,9 +86,6 @@ /* Define to 1 if you have the `backtrace_symbols' function. */ #undef HAVE_BACKTRACE_SYMBOLS -/* Define to 1 if you have the `BIO_get_data' function. */ -#undef HAVE_BIO_GET_DATA - /* Define to 1 if you have the `BIO_meth_new' function. */ #undef HAVE_BIO_METH_NEW diff -Nru postgresql-13-13.13/src/include/port/atomics/generic.h postgresql-13-13.14/src/include/port/atomics/generic.h --- postgresql-13-13.13/src/include/port/atomics/generic.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/port/atomics/generic.h 2024-02-05 21:47:02.000000000 +0000 @@ -83,7 +83,7 @@ static inline bool pg_atomic_test_set_flag_impl(volatile pg_atomic_flag *ptr) { - return pg_atomic_exchange_u32_impl(ptr, &value, 1) == 0; + return pg_atomic_exchange_u32_impl(ptr, 1) == 0; } #define PG_HAVE_ATOMIC_UNLOCKED_TEST_FLAG diff -Nru postgresql-13-13.13/src/include/storage/buf_internals.h postgresql-13-13.14/src/include/storage/buf_internals.h --- postgresql-13-13.13/src/include/storage/buf_internals.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/storage/buf_internals.h 2024-02-05 21:47:02.000000000 +0000 @@ -149,7 +149,7 @@ * is held. Thus buffer header lock holder can do complex updates of the * state variable in single write, simultaneously with lock release (cleaning * BM_LOCKED flag). On the other hand, updating of state without holding - * buffer header lock is restricted to CAS, which insure that BM_LOCKED flag + * buffer header lock is restricted to CAS, which ensures that BM_LOCKED flag * is not set. Atomic increment/decrement, OR/AND etc. are not allowed. * * An exception is that if we have the buffer pinned, its tag can't change diff -Nru postgresql-13-13.13/src/include/storage/lwlock.h postgresql-13-13.14/src/include/storage/lwlock.h --- postgresql-13-13.13/src/include/storage/lwlock.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/storage/lwlock.h 2024-02-05 21:47:02.000000000 +0000 @@ -24,6 +24,14 @@ struct PGPROC; +/* what state of the wait process is a backend in */ +typedef enum LWLockWaitState +{ + LW_WS_NOT_WAITING, /* not currently waiting / woken up */ + LW_WS_WAITING, /* currently waiting */ + LW_WS_PENDING_WAKEUP /* removed from waitlist, but not yet signalled */ +} LWLockWaitState; + /* * Code outside of lwlock.c should not manipulate the contents of this * structure directly, but we have to declare it here to allow LWLocks to be diff -Nru postgresql-13-13.13/src/include/storage/proc.h postgresql-13-13.14/src/include/storage/proc.h --- postgresql-13-13.13/src/include/storage/proc.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/include/storage/proc.h 2024-02-05 21:47:02.000000000 +0000 @@ -140,7 +140,7 @@ bool recoveryConflictPending; /* Info about LWLock the process is currently waiting for, if any. */ - bool lwWaiting; /* true if waiting for an LW lock */ + uint8 lwWaiting; /* see LWLockWaitState */ uint8 lwWaitMode; /* lwlock mode being waited for */ proclist_node lwWaitLink; /* position in LW lock wait list */ diff -Nru postgresql-13-13.13/src/interfaces/libpq/fe-secure-gssapi.c postgresql-13-13.14/src/interfaces/libpq/fe-secure-gssapi.c --- postgresql-13-13.13/src/interfaces/libpq/fe-secure-gssapi.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/interfaces/libpq/fe-secure-gssapi.c 2024-02-05 21:47:02.000000000 +0000 @@ -79,8 +79,8 @@ * On success, returns the number of data bytes consumed (possibly less than * len). On failure, returns -1 with errno set appropriately. If the errno * indicates a non-retryable error, a message is put into conn->errorMessage. - * For retryable errors, caller should call again (passing the same data) - * once the socket is ready. + * For retryable errors, caller should call again (passing the same or more + * data) once the socket is ready. */ ssize_t pg_GSS_write(PGconn *conn, const void *ptr, size_t len) @@ -90,19 +90,25 @@ gss_buffer_desc input, output = GSS_C_EMPTY_BUFFER; ssize_t ret = -1; - size_t bytes_sent = 0; size_t bytes_to_encrypt; size_t bytes_encrypted; gss_ctx_id_t gctx = conn->gctx; /* - * When we get a failure, we must not tell the caller we have successfully - * transmitted everything, else it won't retry. Hence a "success" - * (positive) return value must only count source bytes corresponding to - * fully-transmitted encrypted packets. The amount of source data - * corresponding to the current partly-transmitted packet is remembered in + * When we get a retryable failure, we must not tell the caller we have + * successfully transmitted everything, else it won't retry. For + * simplicity, we claim we haven't transmitted anything until we have + * successfully transmitted all "len" bytes. Between calls, the amount of + * the current input data that's already been encrypted and placed into + * PqGSSSendBuffer (and perhaps transmitted) is remembered in * PqGSSSendConsumed. On a retry, the caller *must* be sending that data * again, so if it offers a len less than that, something is wrong. + * + * Note: it may seem attractive to report partial write completion once + * we've successfully sent any encrypted packets. However, that can cause + * problems for callers; notably, pqPutMsgEnd's heuristic to send only + * full 8K blocks interacts badly with such a hack. We won't save much, + * typically, by letting callers discard data early, so don't risk it. */ if (len < PqGSSSendConsumed) { @@ -135,38 +141,25 @@ */ if (PqGSSSendLength) { - ssize_t ret; + ssize_t retval; ssize_t amount = PqGSSSendLength - PqGSSSendNext; - ret = pqsecure_raw_write(conn, PqGSSSendBuffer + PqGSSSendNext, amount); - if (ret <= 0) - { - /* - * Report any previously-sent data; if there was none, reflect - * the pqsecure_raw_write result up to our caller. When there - * was some, we're effectively assuming that any interesting - * failure condition will recur on the next try. - */ - if (bytes_sent) - return bytes_sent; - return ret; - } + retval = pqsecure_raw_write(conn, PqGSSSendBuffer + PqGSSSendNext, amount); + if (retval <= 0) + return retval; /* * Check if this was a partial write, and if so, move forward that * far in our buffer and try again. */ - if (ret != amount) + if (retval < amount) { - PqGSSSendNext += ret; + PqGSSSendNext += retval; continue; } - /* We've successfully sent whatever data was in that packet. */ - bytes_sent += PqGSSSendConsumed; - - /* All encrypted data was sent, our buffer is empty now. */ - PqGSSSendLength = PqGSSSendNext = PqGSSSendConsumed = 0; + /* We've successfully sent whatever data was in the buffer. */ + PqGSSSendLength = PqGSSSendNext = 0; } /* @@ -192,7 +185,7 @@ /* * Create the next encrypted packet. Any failure here is considered a - * hard failure, so we return -1 even if bytes_sent > 0. + * hard failure, so we return -1 even if some data has been sent. */ major = gss_wrap(&minor, gctx, 1, GSS_C_QOP_DEFAULT, &input, &conf_state, &output); @@ -238,10 +231,13 @@ } /* If we get here, our counters should all match up. */ - Assert(bytes_sent == len); - Assert(bytes_sent == bytes_encrypted); + Assert(len == PqGSSSendConsumed); + Assert(len == bytes_encrypted); + + /* We're reporting all the data as sent, so reset PqGSSSendConsumed. */ + PqGSSSendConsumed = 0; - ret = bytes_sent; + ret = bytes_encrypted; cleanup: /* Release GSSAPI buffer storage, if we didn't already */ diff -Nru postgresql-13-13.13/src/interfaces/libpq/fe-secure-openssl.c postgresql-13-13.14/src/interfaces/libpq/fe-secure-openssl.c --- postgresql-13-13.13/src/interfaces/libpq/fe-secure-openssl.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/interfaces/libpq/fe-secure-openssl.c 2024-02-05 21:47:02.000000000 +0000 @@ -200,7 +200,7 @@ */ goto rloop; case SSL_ERROR_SYSCALL: - if (n < 0) + if (n < 0 && SOCK_ERRNO != 0) { result_errno = SOCK_ERRNO; if (result_errno == EPIPE || @@ -308,7 +308,13 @@ n = 0; break; case SSL_ERROR_SYSCALL: - if (n < 0) + + /* + * If errno is still zero then assume it's a read EOF situation, + * and report EOF. (This seems possible because SSL_write can + * also do reads.) + */ + if (n < 0 && SOCK_ERRNO != 0) { result_errno = SOCK_ERRNO; if (result_errno == EPIPE || result_errno == ECONNRESET) @@ -1305,10 +1311,12 @@ { int r; + SOCK_ERRNO_SET(0); ERR_clear_error(); r = SSL_connect(conn->ssl); if (r <= 0) { + int save_errno = SOCK_ERRNO; int err = SSL_get_error(conn->ssl, r); unsigned long ecode; @@ -1325,10 +1333,10 @@ { char sebuf[PG_STRERROR_R_BUFLEN]; - if (r == -1) + if (r == -1 && save_errno != 0) printfPQExpBuffer(&conn->errorMessage, libpq_gettext("SSL SYSCALL error: %s\n"), - SOCK_STRERROR(SOCK_ERRNO, sebuf, sizeof(sebuf))); + SOCK_STRERROR(save_errno, sebuf, sizeof(sebuf))); else printfPQExpBuffer(&conn->errorMessage, libpq_gettext("SSL SYSCALL error: EOF detected\n")); @@ -1602,11 +1610,7 @@ * to retry; do we need to adopt their logic for that? */ -#ifndef HAVE_BIO_GET_DATA -#define BIO_get_data(bio) (bio->ptr) -#define BIO_set_data(bio, data) (bio->ptr = data) -#endif - +/* protected by ssl_config_mutex */ static BIO_METHOD *my_bio_methods; static int @@ -1614,7 +1618,7 @@ { int res; - res = pqsecure_raw_read((PGconn *) BIO_get_data(h), buf, size); + res = pqsecure_raw_read((PGconn *) BIO_get_app_data(h), buf, size); BIO_clear_retry_flags(h); if (res < 0) { @@ -1644,7 +1648,7 @@ { int res; - res = pqsecure_raw_write((PGconn *) BIO_get_data(h), buf, size); + res = pqsecure_raw_write((PGconn *) BIO_get_app_data(h), buf, size); BIO_clear_retry_flags(h); if (res < 0) { @@ -1672,6 +1676,15 @@ static BIO_METHOD * my_BIO_s_socket(void) { + BIO_METHOD *res; + +#ifdef ENABLE_THREAD_SAFETY + if (pthread_mutex_lock(&ssl_config_mutex)) + return NULL; +#endif + + res = my_bio_methods; + if (!my_bio_methods) { BIO_METHOD *biom = (BIO_METHOD *) BIO_s_socket(); @@ -1680,39 +1693,58 @@ my_bio_index = BIO_get_new_index(); if (my_bio_index == -1) - return NULL; + goto err; my_bio_index |= (BIO_TYPE_DESCRIPTOR | BIO_TYPE_SOURCE_SINK); - my_bio_methods = BIO_meth_new(my_bio_index, "libpq socket"); - if (!my_bio_methods) - return NULL; + res = BIO_meth_new(my_bio_index, "libpq socket"); + if (!res) + goto err; /* * As of this writing, these functions never fail. But check anyway, * like OpenSSL's own examples do. */ - if (!BIO_meth_set_write(my_bio_methods, my_sock_write) || - !BIO_meth_set_read(my_bio_methods, my_sock_read) || - !BIO_meth_set_gets(my_bio_methods, BIO_meth_get_gets(biom)) || - !BIO_meth_set_puts(my_bio_methods, BIO_meth_get_puts(biom)) || - !BIO_meth_set_ctrl(my_bio_methods, BIO_meth_get_ctrl(biom)) || - !BIO_meth_set_create(my_bio_methods, BIO_meth_get_create(biom)) || - !BIO_meth_set_destroy(my_bio_methods, BIO_meth_get_destroy(biom)) || - !BIO_meth_set_callback_ctrl(my_bio_methods, BIO_meth_get_callback_ctrl(biom))) - { - BIO_meth_free(my_bio_methods); - my_bio_methods = NULL; - return NULL; + if (!BIO_meth_set_write(res, my_sock_write) || + !BIO_meth_set_read(res, my_sock_read) || + !BIO_meth_set_gets(res, BIO_meth_get_gets(biom)) || + !BIO_meth_set_puts(res, BIO_meth_get_puts(biom)) || + !BIO_meth_set_ctrl(res, BIO_meth_get_ctrl(biom)) || + !BIO_meth_set_create(res, BIO_meth_get_create(biom)) || + !BIO_meth_set_destroy(res, BIO_meth_get_destroy(biom)) || + !BIO_meth_set_callback_ctrl(res, BIO_meth_get_callback_ctrl(biom))) + { + goto err; } #else - my_bio_methods = malloc(sizeof(BIO_METHOD)); - if (!my_bio_methods) - return NULL; - memcpy(my_bio_methods, biom, sizeof(BIO_METHOD)); - my_bio_methods->bread = my_sock_read; - my_bio_methods->bwrite = my_sock_write; + res = malloc(sizeof(BIO_METHOD)); + if (!res) + goto err; + memcpy(res, biom, sizeof(BIO_METHOD)); + res->bread = my_sock_read; + res->bwrite = my_sock_write; #endif } - return my_bio_methods; + + my_bio_methods = res; + +#ifdef ENABLE_THREAD_SAFETY + pthread_mutex_unlock(&ssl_config_mutex); +#endif + + return res; + +err: +#ifdef HAVE_BIO_METH_NEW + if (res) + BIO_meth_free(res); +#else + if (res) + free(res); +#endif + +#ifdef ENABLE_THREAD_SAFETY + pthread_mutex_unlock(&ssl_config_mutex); +#endif + return NULL; } /* This should exactly match OpenSSL's SSL_set_fd except for using my BIO */ @@ -1735,7 +1767,7 @@ SSLerr(SSL_F_SSL_SET_FD, ERR_R_BUF_LIB); goto err; } - BIO_set_data(bio, conn); + BIO_set_app_data(bio, conn); SSL_set_bio(conn->ssl, bio, bio); BIO_set_fd(bio, fd, BIO_NOCLOSE); diff -Nru postgresql-13-13.13/src/interfaces/libpq/fe-secure.c postgresql-13-13.14/src/interfaces/libpq/fe-secure.c --- postgresql-13-13.13/src/interfaces/libpq/fe-secure.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/interfaces/libpq/fe-secure.c 2024-02-05 21:47:02.000000000 +0000 @@ -242,6 +242,8 @@ int result_errno = 0; char sebuf[PG_STRERROR_R_BUFLEN]; + SOCK_ERRNO_SET(0); + n = recv(conn->sock, ptr, len, 0); if (n < 0) @@ -270,6 +272,11 @@ break; #endif + case 0: + /* If errno didn't get set, treat it as regular EOF */ + n = 0; + break; + default: printfPQExpBuffer(&conn->errorMessage, libpq_gettext("could not receive data from server: %s\n"), diff -Nru postgresql-13-13.13/src/interfaces/libpq/libpq-int.h postgresql-13-13.14/src/interfaces/libpq/libpq-int.h --- postgresql-13-13.13/src/interfaces/libpq/libpq-int.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/interfaces/libpq/libpq-int.h 2024-02-05 21:47:02.000000000 +0000 @@ -501,8 +501,8 @@ int gss_SendLength; /* End of data available in gss_SendBuffer */ int gss_SendNext; /* Next index to send a byte from * gss_SendBuffer */ - int gss_SendConsumed; /* Number of *unencrypted* bytes consumed - * for current contents of gss_SendBuffer */ + int gss_SendConsumed; /* Number of source bytes encrypted but + * not yet reported as sent */ char *gss_RecvBuffer; /* Received, encrypted data */ int gss_RecvLength; /* End of data available in gss_RecvBuffer */ char *gss_ResultBuffer; /* Decryption of data in gss_RecvBuffer */ diff -Nru postgresql-13-13.13/src/pl/plperl/GNUmakefile postgresql-13-13.14/src/pl/plperl/GNUmakefile --- postgresql-13-13.13/src/pl/plperl/GNUmakefile 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/pl/plperl/GNUmakefile 2024-02-05 21:47:02.000000000 +0000 @@ -103,11 +103,11 @@ install-data: installdirs $(INSTALL_DATA) $(addprefix $(srcdir)/, $(DATA)) '$(DESTDIR)$(datadir)/extension/' - $(INSTALL_DATA) $(srcdir)/plperl.h $(srcdir)/ppport.h $(srcdir)/plperl_helpers.h '$(DESTDIR)$(includedir_server)' + $(INSTALL_DATA) $(srcdir)/plperl.h $(srcdir)/plperl_system.h $(srcdir)/ppport.h $(srcdir)/plperl_helpers.h '$(DESTDIR)$(includedir_server)' uninstall-data: rm -f $(addprefix '$(DESTDIR)$(datadir)/extension'/, $(notdir $(DATA))) - rm -f $(addprefix '$(DESTDIR)$(includedir_server)'/, plperl.h ppport.h) + rm -f $(addprefix '$(DESTDIR)$(includedir_server)'/, plperl.h plperl_system.h ppport.h) .PHONY: install-data uninstall-data diff -Nru postgresql-13-13.13/src/pl/plperl/plperl.h postgresql-13-13.14/src/pl/plperl/plperl.h --- postgresql-13-13.13/src/pl/plperl/plperl.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/pl/plperl/plperl.h 2024-02-05 21:47:02.000000000 +0000 @@ -14,199 +14,11 @@ #ifndef PL_PERL_H #define PL_PERL_H -/* stop perl headers from hijacking stdio and other stuff on Windows */ -#ifdef WIN32 -#define WIN32IO_IS_STDIO -#endif /* WIN32 */ - -/* - * Supply a value of PERL_UNUSED_DECL that will satisfy gcc - the one - * perl itself supplies doesn't seem to. - */ -#define PERL_UNUSED_DECL pg_attribute_unused() - -/* - * Sometimes perl carefully scribbles on our *printf macros. - * So we undefine them here and redefine them after it's done its dirty deed. - */ -#undef vsnprintf -#undef snprintf -#undef vsprintf -#undef sprintf -#undef vfprintf -#undef fprintf -#undef vprintf -#undef printf - -/* - * Perl scribbles on the "_" macro too. - */ -#undef _ - -/* - * ActivePerl 5.18 and later are MinGW-built, and their headers use GCC's - * __inline__. Translate to something MSVC recognizes. Also, perl.h sometimes - * defines isnan, so undefine it here and put back the definition later if - * perl.h doesn't. - */ -#ifdef _MSC_VER -#define __inline__ inline -#ifdef isnan -#undef isnan -#endif -/* Work around for using MSVC and Strawberry Perl >= 5.30. */ -#define __builtin_expect(expr, val) (expr) -#endif - -/* - * Regarding bool, both PostgreSQL and Perl might use stdbool.h or not, - * depending on configuration. If both agree, things are relatively harmless. - * If not, things get tricky. If PostgreSQL does but Perl does not, define - * HAS_BOOL here so that Perl does not redefine bool; this avoids compiler - * warnings. If PostgreSQL does not but Perl does, we need to undefine bool - * after we include the Perl headers; see below. - */ -#ifdef PG_USE_STDBOOL -#define HAS_BOOL 1 -#endif - -/* - * Newer versions of the perl headers trigger a lot of warnings with our - * compiler flags (at least -Wdeclaration-after-statement, - * -Wshadow=compatible-local are known to be problematic). The system_header - * pragma hides warnings from within the rest of this file, if supported. - */ -#ifdef HAVE_PRAGMA_GCC_SYSTEM_HEADER -#pragma GCC system_header -#endif - /* - * Get the basic Perl API. We use PERL_NO_GET_CONTEXT mode so that our code - * can compile against MULTIPLICITY Perl builds without including XSUB.h. + * Pull in Perl headers via a wrapper header, to control the scope of + * the system_header pragma therein. */ -#define PERL_NO_GET_CONTEXT -#include "EXTERN.h" -#include "perl.h" - -/* - * We want to include XSUB.h only within .xs files, because on some platforms - * it undesirably redefines a lot of libc functions. But it must appear - * before ppport.h, so use a #define flag to control inclusion here. - */ -#ifdef PG_NEED_PERL_XSUB_H -/* - * On Windows, win32_port.h defines macros for a lot of these same functions. - * To avoid compiler warnings when XSUB.h redefines them, #undef our versions. - */ -#ifdef WIN32 -#undef accept -#undef bind -#undef connect -#undef fopen -#undef kill -#undef listen -#undef lstat -#undef mkdir -#undef open -#undef putenv -#undef recv -#undef rename -#undef select -#undef send -#undef socket -#undef stat -#undef unlink -#endif - -#include "XSUB.h" -#endif - -/* put back our *printf macros ... this must match src/include/port.h */ -#ifdef vsnprintf -#undef vsnprintf -#endif -#ifdef snprintf -#undef snprintf -#endif -#ifdef vsprintf -#undef vsprintf -#endif -#ifdef sprintf -#undef sprintf -#endif -#ifdef vfprintf -#undef vfprintf -#endif -#ifdef fprintf -#undef fprintf -#endif -#ifdef vprintf -#undef vprintf -#endif -#ifdef printf -#undef printf -#endif - -#define vsnprintf pg_vsnprintf -#define snprintf pg_snprintf -#define vsprintf pg_vsprintf -#define sprintf pg_sprintf -#define vfprintf pg_vfprintf -#define fprintf pg_fprintf -#define vprintf pg_vprintf -#define printf(...) pg_printf(__VA_ARGS__) - -/* - * Put back "_" too; but rather than making it just gettext() as the core - * code does, make it dgettext() so that the right things will happen in - * loadable modules (if they've set up TEXTDOMAIN correctly). Note that - * we can't just set TEXTDOMAIN here, because this file is used by more - * extensions than just PL/Perl itself. - */ -#undef _ -#define _(x) dgettext(TEXTDOMAIN, x) - -/* put back the definition of isnan if needed */ -#ifdef _MSC_VER -#ifndef isnan -#define isnan(x) _isnan(x) -#endif -#endif - -/* perl version and platform portability */ -#include "ppport.h" - -/* - * perl might have included stdbool.h. If we also did that earlier (see c.h), - * then that's fine. If not, we probably rejected it for some reason. In - * that case, undef bool and proceed with our own bool. (Note that stdbool.h - * makes bool a macro, but our own replacement is a typedef, so the undef - * makes ours visible again). - */ -#ifndef PG_USE_STDBOOL -#ifdef bool -#undef bool -#endif -#endif - -/* supply HeUTF8 if it's missing - ppport.h doesn't supply it, unfortunately */ -#ifndef HeUTF8 -#define HeUTF8(he) ((HeKLEN(he) == HEf_SVKEY) ? \ - SvUTF8(HeKEY_sv(he)) : \ - (U32)HeKUTF8(he)) -#endif - -/* supply GvCV_set if it's missing - ppport.h doesn't supply it, unfortunately */ -#ifndef GvCV_set -#define GvCV_set(gv, cv) (GvCV(gv) = cv) -#endif - -/* Perl 5.19.4 changed array indices from I32 to SSize_t */ -#if PERL_BCDVERSION >= 0x5019004 -#define AV_SIZE_MAX SSize_t_MAX -#else -#define AV_SIZE_MAX I32_MAX -#endif +#include "plperl_system.h" /* declare routines from plperl.c for access by .xs files */ HV *plperl_spi_exec(char *, int); diff -Nru postgresql-13-13.13/src/pl/plperl/plperl_system.h postgresql-13-13.14/src/pl/plperl/plperl_system.h --- postgresql-13-13.13/src/pl/plperl/plperl_system.h 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.14/src/pl/plperl/plperl_system.h 2024-02-05 21:47:02.000000000 +0000 @@ -0,0 +1,214 @@ +/*------------------------------------------------------------------------- + * + * plperl_system.h + * Pull in Perl's system header files. + * + * We break this out as a separate header file to precisely control + * the scope of the "system_header" pragma. No Postgres-specific + * declarations should be put here. However, we do include some stuff + * that is meant to prevent conflicts between our code and Perl. + * + * Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group + * Portions Copyright (c) 1995, Regents of the University of California + * + * src/pl/plperl/plperl_system.h + */ + +#ifndef PL_PERL_SYSTEM_H +#define PL_PERL_SYSTEM_H + +/* + * Newer versions of the perl headers trigger a lot of warnings with our + * preferred compiler flags (at least -Wdeclaration-after-statement, + * -Wshadow=compatible-local are known to be problematic). The system_header + * pragma hides warnings from within the rest of this file, if supported. + */ +#ifdef HAVE_PRAGMA_GCC_SYSTEM_HEADER +#pragma GCC system_header +#endif + +/* stop perl headers from hijacking stdio and other stuff on Windows */ +#ifdef WIN32 +#define WIN32IO_IS_STDIO +#endif /* WIN32 */ + +/* + * Supply a value of PERL_UNUSED_DECL that will satisfy gcc - the one + * perl itself supplies doesn't seem to. + */ +#define PERL_UNUSED_DECL pg_attribute_unused() + +/* + * Sometimes perl carefully scribbles on our *printf macros. + * So we undefine them here and redefine them after it's done its dirty deed. + */ +#undef vsnprintf +#undef snprintf +#undef vsprintf +#undef sprintf +#undef vfprintf +#undef fprintf +#undef vprintf +#undef printf + +/* + * Perl scribbles on the "_" macro too. + */ +#undef _ + +/* + * ActivePerl 5.18 and later are MinGW-built, and their headers use GCC's + * __inline__. Translate to something MSVC recognizes. Also, perl.h sometimes + * defines isnan, so undefine it here and put back the definition later if + * perl.h doesn't. + */ +#ifdef _MSC_VER +#define __inline__ inline +#ifdef isnan +#undef isnan +#endif +/* Work around for using MSVC and Strawberry Perl >= 5.30. */ +#define __builtin_expect(expr, val) (expr) +#endif + +/* + * Regarding bool, both PostgreSQL and Perl might use stdbool.h or not, + * depending on configuration. If both agree, things are relatively harmless. + * If not, things get tricky. If PostgreSQL does but Perl does not, define + * HAS_BOOL here so that Perl does not redefine bool; this avoids compiler + * warnings. If PostgreSQL does not but Perl does, we need to undefine bool + * after we include the Perl headers; see below. + */ +#ifdef PG_USE_STDBOOL +#define HAS_BOOL 1 +#endif + +/* + * Get the basic Perl API. We use PERL_NO_GET_CONTEXT mode so that our code + * can compile against MULTIPLICITY Perl builds without including XSUB.h. + */ +#define PERL_NO_GET_CONTEXT +#include "EXTERN.h" +#include "perl.h" + +/* + * We want to include XSUB.h only within .xs files, because on some platforms + * it undesirably redefines a lot of libc functions. But it must appear + * before ppport.h, so use a #define flag to control inclusion here. + */ +#ifdef PG_NEED_PERL_XSUB_H +/* + * On Windows, win32_port.h defines macros for a lot of these same functions. + * To avoid compiler warnings when XSUB.h redefines them, #undef our versions. + */ +#ifdef WIN32 +#undef accept +#undef bind +#undef connect +#undef fopen +#undef kill +#undef listen +#undef lstat +#undef mkdir +#undef open +#undef putenv +#undef recv +#undef rename +#undef select +#undef send +#undef socket +#undef stat +#undef unlink +#endif + +#include "XSUB.h" +#endif + +/* put back our *printf macros ... this must match src/include/port.h */ +#ifdef vsnprintf +#undef vsnprintf +#endif +#ifdef snprintf +#undef snprintf +#endif +#ifdef vsprintf +#undef vsprintf +#endif +#ifdef sprintf +#undef sprintf +#endif +#ifdef vfprintf +#undef vfprintf +#endif +#ifdef fprintf +#undef fprintf +#endif +#ifdef vprintf +#undef vprintf +#endif +#ifdef printf +#undef printf +#endif + +#define vsnprintf pg_vsnprintf +#define snprintf pg_snprintf +#define vsprintf pg_vsprintf +#define sprintf pg_sprintf +#define vfprintf pg_vfprintf +#define fprintf pg_fprintf +#define vprintf pg_vprintf +#define printf(...) pg_printf(__VA_ARGS__) + +/* + * Put back "_" too; but rather than making it just gettext() as the core + * code does, make it dgettext() so that the right things will happen in + * loadable modules (if they've set up TEXTDOMAIN correctly). Note that + * we can't just set TEXTDOMAIN here, because this file is used by more + * extensions than just PL/Perl itself. + */ +#undef _ +#define _(x) dgettext(TEXTDOMAIN, x) + +/* put back the definition of isnan if needed */ +#ifdef _MSC_VER +#ifndef isnan +#define isnan(x) _isnan(x) +#endif +#endif + +/* perl version and platform portability */ +#include "ppport.h" + +/* + * perl might have included stdbool.h. If we also did that earlier (see c.h), + * then that's fine. If not, we probably rejected it for some reason. In + * that case, undef bool and proceed with our own bool. (Note that stdbool.h + * makes bool a macro, but our own replacement is a typedef, so the undef + * makes ours visible again). + */ +#ifndef PG_USE_STDBOOL +#ifdef bool +#undef bool +#endif +#endif + +/* supply HeUTF8 if it's missing - ppport.h doesn't supply it, unfortunately */ +#ifndef HeUTF8 +#define HeUTF8(he) ((HeKLEN(he) == HEf_SVKEY) ? \ + SvUTF8(HeKEY_sv(he)) : \ + (U32)HeKUTF8(he)) +#endif + +/* supply GvCV_set if it's missing - ppport.h doesn't supply it, unfortunately */ +#ifndef GvCV_set +#define GvCV_set(gv, cv) (GvCV(gv) = cv) +#endif + +/* Perl 5.19.4 changed array indices from I32 to SSize_t */ +#if PERL_BCDVERSION >= 0x5019004 +#define AV_SIZE_MAX SSize_t_MAX +#else +#define AV_SIZE_MAX I32_MAX +#endif + +#endif /* PL_PERL_SYSTEM_H */ diff -Nru postgresql-13-13.13/src/pl/plpython/Makefile postgresql-13-13.14/src/pl/plpython/Makefile --- postgresql-13-13.13/src/pl/plpython/Makefile 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/pl/plpython/Makefile 2024-02-05 21:47:02.000000000 +0000 @@ -42,6 +42,7 @@ # header files to install - it's not clear which of these might be needed # so install them all. INCS = plpython.h \ + plpython_system.h \ plpy_cursorobject.h \ plpy_elog.h \ plpy_exec.h \ @@ -131,7 +132,7 @@ uninstall-data: rm -f $(addprefix '$(DESTDIR)$(datadir)/extension'/, $(notdir $(DATA))) - rm -f $(addprefix '$(DESTDIR)$(includedir_server)'/, plpython.h plpy_util.h) + rm -f $(addprefix '$(DESTDIR)$(includedir_server)'/, $(INCS)) .PHONY: install-data uninstall-data diff -Nru postgresql-13-13.13/src/pl/plpython/plpython.h postgresql-13-13.14/src/pl/plpython/plpython.h --- postgresql-13-13.13/src/pl/plpython/plpython.h 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/pl/plpython/plpython.h 2024-02-05 21:47:02.000000000 +0000 @@ -22,113 +22,15 @@ #endif /* - * Undefine some things that get (re)defined in the Python headers. They aren't - * used by the PL/Python code, and all PostgreSQL headers should be included - * earlier, so this should be pretty safe. + * Pull in Python headers via a wrapper header, to control the scope of + * the system_header pragma therein. */ -#undef _POSIX_C_SOURCE -#undef _XOPEN_SOURCE - -/* - * Sometimes python carefully scribbles on our *printf macros. - * So we undefine them here and redefine them after it's done its dirty deed. - */ -#undef vsnprintf -#undef snprintf -#undef vsprintf -#undef sprintf -#undef vfprintf -#undef fprintf -#undef vprintf -#undef printf - -#if defined(_MSC_VER) && defined(_DEBUG) -/* Python uses #pragma to bring in a non-default libpython on VC++ if - * _DEBUG is defined */ -#undef _DEBUG -/* Also hide away errcode, since we load Python.h before postgres.h */ -#define errcode __msvc_errcode -#include -#undef errcode -#define _DEBUG -#elif defined (_MSC_VER) -#define errcode __msvc_errcode -#include -#undef errcode -#else -#include -#endif - -/* - * Python 2/3 strings/unicode/bytes handling. Python 2 has strings - * and unicode, Python 3 has strings, which are unicode on the C - * level, and bytes. The porting convention, which is similarly used - * in Python 2.6, is that "Unicode" is always unicode, and "Bytes" are - * bytes in Python 3 and strings in Python 2. Since we keep - * supporting Python 2 and its usual strings, we provide a - * compatibility layer for Python 3 that when asked to convert a C - * string to a Python string it converts the C string from the - * PostgreSQL server encoding to a Python Unicode object. - */ -#if PY_MAJOR_VERSION >= 3 -#define PyString_Check(x) 0 -#define PyString_AsString(x) PLyUnicode_AsString(x) -#define PyString_FromString(x) PLyUnicode_FromString(x) -#define PyString_FromStringAndSize(x, size) PLyUnicode_FromStringAndSize(x, size) -#endif - -/* - * Python 3 only has long. - */ -#if PY_MAJOR_VERSION >= 3 -#define PyInt_FromLong(x) PyLong_FromLong(x) -#define PyInt_AsLong(x) PyLong_AsLong(x) -#endif - -/* Python 3 removed the Py_TPFLAGS_HAVE_ITER flag */ -#if PY_MAJOR_VERSION >= 3 -#define Py_TPFLAGS_HAVE_ITER 0 -#endif +#include "plpython_system.h" /* define our text domain for translations */ #undef TEXTDOMAIN #define TEXTDOMAIN PG_TEXTDOMAIN("plpython") -/* put back our *printf macros ... this must match src/include/port.h */ -#ifdef vsnprintf -#undef vsnprintf -#endif -#ifdef snprintf -#undef snprintf -#endif -#ifdef vsprintf -#undef vsprintf -#endif -#ifdef sprintf -#undef sprintf -#endif -#ifdef vfprintf -#undef vfprintf -#endif -#ifdef fprintf -#undef fprintf -#endif -#ifdef vprintf -#undef vprintf -#endif -#ifdef printf -#undef printf -#endif - -#define vsnprintf pg_vsnprintf -#define snprintf pg_snprintf -#define vsprintf pg_vsprintf -#define sprintf pg_sprintf -#define vfprintf pg_vfprintf -#define fprintf pg_fprintf -#define vprintf pg_vprintf -#define printf(...) pg_printf(__VA_ARGS__) - /* * Used throughout, and also by the Python 2/3 porting layer, so it's easier to * just include it everywhere. diff -Nru postgresql-13-13.13/src/pl/plpython/plpython_system.h postgresql-13-13.14/src/pl/plpython/plpython_system.h --- postgresql-13-13.13/src/pl/plpython/plpython_system.h 1970-01-01 00:00:00.000000000 +0000 +++ postgresql-13-13.14/src/pl/plpython/plpython_system.h 2024-02-05 21:47:02.000000000 +0000 @@ -0,0 +1,134 @@ +/*------------------------------------------------------------------------- + * + * plpython_system.h - pull in Python's system header files + * + * We break this out as a separate header file to precisely control + * the scope of the "system_header" pragma. No Postgres-specific + * declarations should be put here. However, we do include some stuff + * that is meant to prevent conflicts between our code and Python. + * + * Portions Copyright (c) 1996-2023, PostgreSQL Global Development Group + * Portions Copyright (c) 1994, Regents of the University of California + * + * src/pl/plpython/plpython_system.h + * + *------------------------------------------------------------------------- + */ +#ifndef PLPYTHON_SYSTEM_H +#define PLPYTHON_SYSTEM_H + +/* + * Newer versions of the Python headers trigger a lot of warnings with our + * preferred compiler flags (at least -Wdeclaration-after-statement is known + * to be problematic). The system_header pragma hides warnings from within + * the rest of this file, if supported. + */ +#ifdef HAVE_PRAGMA_GCC_SYSTEM_HEADER +#pragma GCC system_header +#endif + +/* + * Undefine some things that get (re)defined in the Python headers. They aren't + * used by the PL/Python code, and all PostgreSQL headers should be included + * earlier, so this should be pretty safe. + */ +#undef _POSIX_C_SOURCE +#undef _XOPEN_SOURCE + +/* + * Sometimes python carefully scribbles on our *printf macros. + * So we undefine them here and redefine them after it's done its dirty deed. + */ +#undef vsnprintf +#undef snprintf +#undef vsprintf +#undef sprintf +#undef vfprintf +#undef fprintf +#undef vprintf +#undef printf + +#if defined(_MSC_VER) && defined(_DEBUG) +/* Python uses #pragma to bring in a non-default libpython on VC++ if + * _DEBUG is defined */ +#undef _DEBUG +/* Also hide away errcode, since we load Python.h before postgres.h */ +#define errcode __msvc_errcode +#include +#undef errcode +#define _DEBUG +#elif defined (_MSC_VER) +#define errcode __msvc_errcode +#include +#undef errcode +#else +#include +#endif + +/* + * Python 2/3 strings/unicode/bytes handling. Python 2 has strings + * and unicode, Python 3 has strings, which are unicode on the C + * level, and bytes. The porting convention, which is similarly used + * in Python 2.6, is that "Unicode" is always unicode, and "Bytes" are + * bytes in Python 3 and strings in Python 2. Since we keep + * supporting Python 2 and its usual strings, we provide a + * compatibility layer for Python 3 that when asked to convert a C + * string to a Python string it converts the C string from the + * PostgreSQL server encoding to a Python Unicode object. + */ +#if PY_MAJOR_VERSION >= 3 +#define PyString_Check(x) 0 +#define PyString_AsString(x) PLyUnicode_AsString(x) +#define PyString_FromString(x) PLyUnicode_FromString(x) +#define PyString_FromStringAndSize(x, size) PLyUnicode_FromStringAndSize(x, size) +#endif + +/* + * Python 3 only has long. + */ +#if PY_MAJOR_VERSION >= 3 +#define PyInt_FromLong(x) PyLong_FromLong(x) +#define PyInt_AsLong(x) PyLong_AsLong(x) +#endif + +/* Python 3 removed the Py_TPFLAGS_HAVE_ITER flag */ +#if PY_MAJOR_VERSION >= 3 +#define Py_TPFLAGS_HAVE_ITER 0 +#endif + +/* put back our *printf macros ... this must match src/include/port.h */ +#ifdef vsnprintf +#undef vsnprintf +#endif +#ifdef snprintf +#undef snprintf +#endif +#ifdef vsprintf +#undef vsprintf +#endif +#ifdef sprintf +#undef sprintf +#endif +#ifdef vfprintf +#undef vfprintf +#endif +#ifdef fprintf +#undef fprintf +#endif +#ifdef vprintf +#undef vprintf +#endif +#ifdef printf +#undef printf +#endif + +#define vsnprintf pg_vsnprintf +#define snprintf pg_snprintf +#define vsprintf pg_vsprintf +#define sprintf pg_sprintf +#define vfprintf pg_vfprintf +#define fprintf pg_fprintf +#define vprintf pg_vprintf +#define printf(...) pg_printf(__VA_ARGS__) + +#endif /* PLPYTHON_SYSTEM_H */ diff -Nru postgresql-13-13.13/src/test/modules/test_pg_dump/t/001_base.pl postgresql-13-13.14/src/test/modules/test_pg_dump/t/001_base.pl --- postgresql-13-13.13/src/test/modules/test_pg_dump/t/001_base.pl 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/modules/test_pg_dump/t/001_base.pl 2024-02-05 21:47:02.000000000 +0000 @@ -169,6 +169,19 @@ 'postgres', ], }, + + # regress_dump_login_role shouldn't need SELECT rights on internal + # (undumped) extension tables + privileged_internals => { + dump_cmd => [ + 'pg_dump', '--no-sync', "--file=$tempdir/privileged_internals.sql", + # these two tables are irrelevant to the test case + '--exclude-table=regress_pg_dump_schema.external_tab', + '--exclude-table=regress_pg_dump_schema.extdependtab', + '--username=regress_dump_login_role', 'postgres', + ], + }, + schema_only => { dump_cmd => [ 'pg_dump', '--no-sync', "--file=$tempdir/schema_only.sql", @@ -235,7 +248,8 @@ defaults => 1, exclude_table => 1, no_privs => 1, - no_owner => 1,); + no_owner => 1, + privileged_internals => 1,); my %tests = ( 'ALTER EXTENSION test_pg_dump' => { @@ -271,6 +285,16 @@ like => { pg_dumpall_globals => 1, }, }, + 'CREATE ROLE regress_dump_login_role' => { + create_order => 1, + create_sql => 'CREATE ROLE regress_dump_login_role LOGIN;', + regexp => qr/^ + \QCREATE ROLE regress_dump_login_role;\E + \n\QALTER ROLE regress_dump_login_role WITH \E.*\Q LOGIN \E.*; + \n/xm, + like => { pg_dumpall_globals => 1, }, + }, + 'CREATE SEQUENCE regress_pg_dump_table_col1_seq' => { regexp => qr/^ \QCREATE SEQUENCE public.regress_pg_dump_table_col1_seq\E @@ -611,6 +635,7 @@ data_only => 1, extension_schema => 1, pg_dumpall_globals => 1, + privileged_internals => 1, section_data => 1, section_pre_data => 1, }, @@ -625,6 +650,7 @@ data_only => 1, extension_schema => 1, pg_dumpall_globals => 1, + privileged_internals => 1, section_data => 1, section_pre_data => 1, }, @@ -644,13 +670,14 @@ schema_only => 1, section_pre_data => 1, }, + unlike => { privileged_internals => 1 }, },); ######################################### # Create a PG instance to test actually dumping from my $node = get_new_node('main'); -$node->init; +$node->init('auth_extra' => [ '--create-role', 'regress_dump_login_role' ]); $node->start; my $port = $node->port; diff -Nru postgresql-13-13.13/src/test/modules/test_pg_dump/test_pg_dump--1.0.sql postgresql-13-13.14/src/test/modules/test_pg_dump/test_pg_dump--1.0.sql --- postgresql-13-13.13/src/test/modules/test_pg_dump/test_pg_dump--1.0.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/modules/test_pg_dump/test_pg_dump--1.0.sql 2024-02-05 21:47:02.000000000 +0000 @@ -12,11 +12,13 @@ CREATE SEQUENCE regress_seq_dumpable; SELECT pg_catalog.pg_extension_config_dump('regress_seq_dumpable', ''); +GRANT SELECT ON SEQUENCE regress_seq_dumpable TO public; CREATE TABLE regress_table_dumpable ( col1 int check (col1 > 0) ); SELECT pg_catalog.pg_extension_config_dump('regress_table_dumpable', ''); +GRANT SELECT ON regress_table_dumpable TO public; CREATE SCHEMA regress_pg_dump_schema; diff -Nru postgresql-13-13.13/src/test/regress/expected/fast_default.out postgresql-13-13.14/src/test/regress/expected/fast_default.out --- postgresql-13-13.13/src/test/regress/expected/fast_default.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/fast_default.out 2024-02-05 21:47:02.000000000 +0000 @@ -272,7 +272,25 @@ Rewritten (1 row) +-- check that we notice insertion of a volatile default argument +CREATE FUNCTION foolme(timestamptz DEFAULT clock_timestamp()) + RETURNS timestamptz + IMMUTABLE AS 'select $1' LANGUAGE sql; +ALTER TABLE T ADD COLUMN c3 timestamptz DEFAULT foolme(); +NOTICE: rewriting table t for reason 2 +SELECT attname, atthasmissing, attmissingval FROM pg_attribute + WHERE attrelid = 't'::regclass AND attnum > 0 + ORDER BY attnum; + attname | atthasmissing | attmissingval +---------+---------------+--------------- + pk | f | + c1 | f | + c2 | f | + c3 | f | +(4 rows) + DROP TABLE T; +DROP FUNCTION foolme(timestamptz); -- Simple querie CREATE TABLE T (pk INT NOT NULL PRIMARY KEY); SELECT set('t'); diff -Nru postgresql-13-13.13/src/test/regress/expected/generated.out postgresql-13-13.14/src/test/regress/expected/generated.out --- postgresql-13-13.13/src/test/regress/expected/generated.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/generated.out 2024-02-05 21:47:02.000000000 +0000 @@ -61,6 +61,9 @@ -- generation expression must be immutable CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) STORED); ERROR: generation expression is not immutable +-- ... but be sure that the immutability test is accurate +CREATE TABLE gtest2 (a int, b text GENERATED ALWAYS AS (a || ' sec') STORED); +DROP TABLE gtest2; -- cannot have default/identity and generated CREATE TABLE gtest_err_5a (a int PRIMARY KEY, b int DEFAULT 5 GENERATED ALWAYS AS (a * 2) STORED); ERROR: both default and generation expression specified for column "b" of table "gtest_err_5a" diff -Nru postgresql-13-13.13/src/test/regress/expected/horology.out postgresql-13-13.14/src/test/regress/expected/horology.out --- postgresql-13-13.13/src/test/regress/expected/horology.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/horology.out 2024-02-05 21:47:02.000000000 +0000 @@ -373,6 +373,8 @@ Sun Dec 31 00:00:00 294276 (1 row) +SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range"; +ERROR: timestamp out of range SELECT timestamp without time zone '12/31/294276' - timestamp without time zone '12/23/1999' AS "106751991 Days"; 106751991 Days ------------------ @@ -633,6 +635,8 @@ Fri Dec 31 23:59:59 1999 PST (1 row) +SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range"; +ERROR: timestamp out of range SELECT (timestamp with time zone 'today' = (timestamp with time zone 'yesterday' + interval '1 day')) as "True"; True ------ diff -Nru postgresql-13-13.13/src/test/regress/expected/indexing.out postgresql-13-13.14/src/test/regress/expected/indexing.out --- postgresql-13-13.13/src/test/regress/expected/indexing.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/indexing.out 2024-02-05 21:47:02.000000000 +0000 @@ -1281,6 +1281,45 @@ (8 rows) drop table idxpart; +-- Test some other non-btree index types +create table idxpart (a int, b text, c int[]) partition by range (a); +create table idxpart1 partition of idxpart for values from (0) to (100000); +set enable_seqscan to off; +create index idxpart_brin on idxpart using brin(b); +explain (costs off) select * from idxpart where b = 'abcd'; + QUERY PLAN +------------------------------------------- + Bitmap Heap Scan on idxpart1 idxpart + Recheck Cond: (b = 'abcd'::text) + -> Bitmap Index Scan on idxpart1_b_idx + Index Cond: (b = 'abcd'::text) +(4 rows) + +drop index idxpart_brin; +create index idxpart_spgist on idxpart using spgist(b); +explain (costs off) select * from idxpart where b = 'abcd'; + QUERY PLAN +------------------------------------------- + Bitmap Heap Scan on idxpart1 idxpart + Recheck Cond: (b = 'abcd'::text) + -> Bitmap Index Scan on idxpart1_b_idx + Index Cond: (b = 'abcd'::text) +(4 rows) + +drop index idxpart_spgist; +create index idxpart_gin on idxpart using gin(c); +explain (costs off) select * from idxpart where c @> array[42]; + QUERY PLAN +---------------------------------------------- + Bitmap Heap Scan on idxpart1 idxpart + Recheck Cond: (c @> '{42}'::integer[]) + -> Bitmap Index Scan on idxpart1_c_idx + Index Cond: (c @> '{42}'::integer[]) +(4 rows) + +drop index idxpart_gin; +reset enable_seqscan; +drop table idxpart; -- intentionally leave some objects around create table idxpart (a int) partition by range (a); create table idxpart1 partition of idxpart for values from (0) to (100); diff -Nru postgresql-13-13.13/src/test/regress/expected/inherit.out postgresql-13-13.14/src/test/regress/expected/inherit.out --- postgresql-13-13.13/src/test/regress/expected/inherit.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/inherit.out 2024-02-05 21:47:02.000000000 +0000 @@ -1063,6 +1063,23 @@ inhs1 DROP TABLE inhts; +-- Test for adding a column to a parent table with complex inheritance +CREATE TABLE inhta (); +CREATE TABLE inhtb () INHERITS (inhta); +CREATE TABLE inhtc () INHERITS (inhtb); +CREATE TABLE inhtd () INHERITS (inhta, inhtb, inhtc); +ALTER TABLE inhta ADD COLUMN i int; +NOTICE: merging definition of column "i" for child "inhtd" +NOTICE: merging definition of column "i" for child "inhtd" +\d+ inhta + Table "public.inhta" + Column | Type | Collation | Nullable | Default | Storage | Stats target | Description +--------+---------+-----------+----------+---------+---------+--------------+------------- + i | integer | | | | plain | | +Child tables: inhtb, + inhtd + +DROP TABLE inhta, inhtb, inhtc, inhtd; -- Test for renaming in diamond inheritance CREATE TABLE inht2 (x int) INHERITS (inht1); CREATE TABLE inht3 (y int) INHERITS (inht1); diff -Nru postgresql-13-13.13/src/test/regress/expected/int8.out postgresql-13-13.14/src/test/regress/expected/int8.out --- postgresql-13-13.13/src/test/regress/expected/int8.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/int8.out 2024-02-05 21:47:02.000000000 +0000 @@ -659,6 +659,8 @@ select -('-9223372036854775808'::int8); ERROR: bigint out of range +select 0::int8 - '-9223372036854775808'::int8; +ERROR: bigint out of range select '9223372036854775800'::int8 + '9223372036854775800'::int8; ERROR: bigint out of range select '-9223372036854775800'::int8 + '-9223372036854775800'::int8; diff -Nru postgresql-13-13.13/src/test/regress/expected/interval.out postgresql-13-13.14/src/test/regress/expected/interval.out --- postgresql-13-13.13/src/test/regress/expected/interval.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/interval.out 2024-02-05 21:47:02.000000000 +0000 @@ -357,6 +357,19 @@ | @ 5 mons 12 hours (10 rows) +-- multiplication and division overflow test cases +SELECT '3000000 months'::interval * 1000; +ERROR: interval out of range +SELECT '3000000 months'::interval / 0.001; +ERROR: interval out of range +SELECT '3000000 days'::interval * 1000; +ERROR: interval out of range +SELECT '3000000 days'::interval / 0.001; +ERROR: interval out of range +SELECT '1 month 2146410 days'::interval * 1000.5002; +ERROR: interval out of range +SELECT make_interval(0, 0, 0, 0, 0, 0, 4611686018427.387904) / 0.1; +ERROR: interval out of range -- test avg(interval), which is somewhat fragile since people have been -- known to change the allowed input syntax for type interval without -- updating pg_aggregate.agginitval diff -Nru postgresql-13-13.13/src/test/regress/expected/join.out postgresql-13-13.14/src/test/regress/expected/join.out --- postgresql-13-13.13/src/test/regress/expected/join.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/join.out 2024-02-05 21:47:02.000000000 +0000 @@ -5696,6 +5696,32 @@ Output: (COALESCE((COALESCE(b.q2, '42'::bigint)), d.q2)) (24 rows) +-- another case requiring nested PlaceHolderVars +explain (verbose, costs off) +select * from + (select 0 as val0) as ss0 + left join (select 1 as val) as ss1 on true + left join lateral (select ss1.val as val_filtered where false) as ss2 on true; + QUERY PLAN +-------------------------------- + Nested Loop Left Join + Output: 0, (1), ((1)) + -> Result + Output: 1 + -> Result + Output: (1) + One-Time Filter: false +(7 rows) + +select * from + (select 0 as val0) as ss0 + left join (select 1 as val) as ss1 on true + left join lateral (select ss1.val as val_filtered where false) as ss2 on true; + val0 | val | val_filtered +------+-----+-------------- + 0 | 1 | +(1 row) + -- case that breaks the old ph_may_need optimization explain (verbose, costs off) select c.*,a.*,ss1.q1,ss2.q1,ss3.* from diff -Nru postgresql-13-13.13/src/test/regress/expected/matview.out postgresql-13-13.14/src/test/regress/expected/matview.out --- postgresql-13-13.13/src/test/regress/expected/matview.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/matview.out 2024-02-05 21:47:02.000000000 +0000 @@ -572,6 +572,22 @@ REFRESH MATERIALIZED VIEW CONCURRENTLY mvtest_mv_foo; DROP OWNED BY regress_user_mvtest CASCADE; DROP ROLE regress_user_mvtest; +-- Concurrent refresh requires a unique index on the materialized +-- view. Test what happens if it's dropped during the refresh. +CREATE OR REPLACE FUNCTION mvtest_drop_the_index() + RETURNS bool AS $$ +BEGIN + EXECUTE 'DROP INDEX IF EXISTS mvtest_drop_idx'; + RETURN true; +END; +$$ LANGUAGE plpgsql; +CREATE MATERIALIZED VIEW drop_idx_matview AS + SELECT 1 as i WHERE mvtest_drop_the_index(); +NOTICE: index "mvtest_drop_idx" does not exist, skipping +CREATE UNIQUE INDEX mvtest_drop_idx ON drop_idx_matview (i); +REFRESH MATERIALIZED VIEW CONCURRENTLY drop_idx_matview; +ERROR: could not find suitable unique index on materialized view +DROP MATERIALIZED VIEW drop_idx_matview; -- clean up -- make sure that create WITH NO DATA works via SPI BEGIN; CREATE FUNCTION mvtest_func() diff -Nru postgresql-13-13.13/src/test/regress/expected/opr_sanity.out postgresql-13-13.14/src/test/regress/expected/opr_sanity.out --- postgresql-13-13.13/src/test/regress/expected/opr_sanity.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/opr_sanity.out 2024-02-05 21:47:02.000000000 +0000 @@ -1903,7 +1903,7 @@ -- Check for table amhandler functions with the wrong signature SELECT p1.oid, p1.amname, p2.oid, p2.proname FROM pg_am AS p1, pg_proc AS p2 -WHERE p2.oid = p1.amhandler AND p1.amtype = 's' AND +WHERE p2.oid = p1.amhandler AND p1.amtype = 't' AND (p2.prorettype != 'table_am_handler'::regtype OR p2.proretset OR p2.pronargs != 1 diff -Nru postgresql-13-13.13/src/test/regress/expected/partition_join.out postgresql-13-13.14/src/test/regress/expected/partition_join.out --- postgresql-13-13.13/src/test/regress/expected/partition_join.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/partition_join.out 2024-02-05 21:47:02.000000000 +0000 @@ -459,6 +459,99 @@ 550 | | (12 rows) +SET max_parallel_workers_per_gather = 0; +-- If there are lateral references to the other relation in sample scan, +-- we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT * FROM prt1 t1 JOIN LATERAL + (SELECT * FROM prt1 t2 TABLESAMPLE SYSTEM (t1.a) REPEATABLE(t1.b)) s + ON t1.a = s.a; + QUERY PLAN +--------------------------------------------------------- + Nested Loop + -> Append + -> Seq Scan on prt1_p1 t1_1 + -> Seq Scan on prt1_p2 t1_2 + -> Seq Scan on prt1_p3 t1_3 + -> Append + -> Sample Scan on prt1_p1 t2_1 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: (t1.a = a) + -> Sample Scan on prt1_p2 t2_2 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: (t1.a = a) + -> Sample Scan on prt1_p3 t2_3 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: (t1.a = a) +(15 rows) + +-- If there are lateral references to the other relation in scan's restriction +-- clauses, we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.a; + QUERY PLAN +--------------------------------------------------------------- + Aggregate + -> Nested Loop + -> Append + -> Seq Scan on prt1_p1 t1_1 + -> Seq Scan on prt1_p2 t1_2 + -> Seq Scan on prt1_p3 t1_3 + -> Append + -> Index Scan using iprt2_p1_b on prt2_p1 t2_1 + Index Cond: (b = t1.a) + Filter: (t1.b = a) + -> Index Scan using iprt2_p2_b on prt2_p2 t2_2 + Index Cond: (b = t1.a) + Filter: (t1.b = a) + -> Index Scan using iprt2_p3_b on prt2_p3 t2_3 + Index Cond: (b = t1.a) + Filter: (t1.b = a) +(16 rows) + +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.a; + count +------- + 100 +(1 row) + +EXPLAIN (COSTS OFF) +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.b; + QUERY PLAN +-------------------------------------------------------------------- + Aggregate + -> Nested Loop + -> Append + -> Seq Scan on prt1_p1 t1_1 + -> Seq Scan on prt1_p2 t1_2 + -> Seq Scan on prt1_p3 t1_3 + -> Append + -> Index Only Scan using iprt2_p1_b on prt2_p1 t2_1 + Index Cond: (b = t1.a) + Filter: (b = t1.b) + -> Index Only Scan using iprt2_p2_b on prt2_p2 t2_2 + Index Cond: (b = t1.a) + Filter: (b = t1.b) + -> Index Only Scan using iprt2_p3_b on prt2_p3 t2_3 + Index Cond: (b = t1.a) + Filter: (b = t1.b) +(16 rows) + +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.b; + count +------- + 5 +(1 row) + +RESET max_parallel_workers_per_gather; -- bug with inadequate sort key representation SET enable_partitionwise_aggregate TO true; SET enable_hashjoin TO false; @@ -1897,6 +1990,80 @@ 550 | 0 | 0002 | | | | | (12 rows) +SET max_parallel_workers_per_gather = 0; +-- If there are lateral references to the other relation in sample scan, +-- we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT * FROM prt1_l t1 JOIN LATERAL + (SELECT * FROM prt1_l t2 TABLESAMPLE SYSTEM (t1.a) REPEATABLE(t1.b)) s + ON t1.a = s.a AND t1.b = s.b AND t1.c = s.c; + QUERY PLAN +---------------------------------------------------------------------------------- + Nested Loop + -> Append + -> Seq Scan on prt1_l_p1 t1_1 + -> Seq Scan on prt1_l_p2_p1 t1_2 + -> Seq Scan on prt1_l_p2_p2 t1_3 + -> Seq Scan on prt1_l_p3_p1 t1_4 + -> Seq Scan on prt1_l_p3_p2 t1_5 + -> Append + -> Sample Scan on prt1_l_p1 t2_1 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: ((t1.a = a) AND (t1.b = b) AND ((t1.c)::text = (c)::text)) + -> Sample Scan on prt1_l_p2_p1 t2_2 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: ((t1.a = a) AND (t1.b = b) AND ((t1.c)::text = (c)::text)) + -> Sample Scan on prt1_l_p2_p2 t2_3 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: ((t1.a = a) AND (t1.b = b) AND ((t1.c)::text = (c)::text)) + -> Sample Scan on prt1_l_p3_p1 t2_4 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: ((t1.a = a) AND (t1.b = b) AND ((t1.c)::text = (c)::text)) + -> Sample Scan on prt1_l_p3_p2 t2_5 + Sampling: system (t1.a) REPEATABLE (t1.b) + Filter: ((t1.a = a) AND (t1.b = b) AND ((t1.c)::text = (c)::text)) +(23 rows) + +-- If there are lateral references to the other relation in scan's restriction +-- clauses, we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT COUNT(*) FROM prt1_l t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2_l t2) s + ON t1.a = s.b AND t1.b = s.a AND t1.c = s.c + WHERE s.t1b = s.a; + QUERY PLAN +------------------------------------------------------------------------------------------------------- + Aggregate + -> Nested Loop + -> Append + -> Seq Scan on prt1_l_p1 t1_1 + -> Seq Scan on prt1_l_p2_p1 t1_2 + -> Seq Scan on prt1_l_p2_p2 t1_3 + -> Seq Scan on prt1_l_p3_p1 t1_4 + -> Seq Scan on prt1_l_p3_p2 t1_5 + -> Append + -> Seq Scan on prt2_l_p1 t2_1 + Filter: ((a = t1.b) AND (t1.a = b) AND (t1.b = a) AND ((t1.c)::text = (c)::text)) + -> Seq Scan on prt2_l_p2_p1 t2_2 + Filter: ((a = t1.b) AND (t1.a = b) AND (t1.b = a) AND ((t1.c)::text = (c)::text)) + -> Seq Scan on prt2_l_p2_p2 t2_3 + Filter: ((a = t1.b) AND (t1.a = b) AND (t1.b = a) AND ((t1.c)::text = (c)::text)) + -> Seq Scan on prt2_l_p3_p1 t2_4 + Filter: ((a = t1.b) AND (t1.a = b) AND (t1.b = a) AND ((t1.c)::text = (c)::text)) + -> Seq Scan on prt2_l_p3_p2 t2_5 + Filter: ((a = t1.b) AND (t1.a = b) AND (t1.b = a) AND ((t1.c)::text = (c)::text)) +(19 rows) + +SELECT COUNT(*) FROM prt1_l t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2_l t2) s + ON t1.a = s.b AND t1.b = s.a AND t1.c = s.c + WHERE s.t1b = s.a; + count +------- + 100 +(1 row) + +RESET max_parallel_workers_per_gather; -- join with one side empty EXPLAIN (COSTS OFF) SELECT t1.a, t1.c, t2.b, t2.c FROM (SELECT * FROM prt1_l WHERE a = 1 AND a = 2) t1 RIGHT JOIN prt2_l t2 ON t1.a = t2.b AND t1.b = t2.a AND t1.c = t2.c; diff -Nru postgresql-13-13.13/src/test/regress/expected/tsdicts.out postgresql-13-13.14/src/test/regress/expected/tsdicts.out --- postgresql-13-13.13/src/test/regress/expected/tsdicts.out 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/expected/tsdicts.out 2024-02-05 21:47:02.000000000 +0000 @@ -687,3 +687,37 @@ "AffFile" = ispell_sample ); ERROR: unrecognized Ispell parameter: "DictFile" +-- Test grammar for configurations +CREATE TEXT SEARCH CONFIGURATION dummy_tst (COPY=english); +-- Overriden mapping change with duplicated tokens. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + ALTER MAPPING FOR word, word WITH ispell; +-- Not a token supported by the configuration's parser, fails. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING FOR not_a_token, not_a_token; +ERROR: token type "not_a_token" does not exist +-- Not a token supported by the configuration's parser, fails even +-- with IF EXISTS. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING IF EXISTS FOR not_a_token, not_a_token; +ERROR: token type "not_a_token" does not exist +-- Token supported by the configuration's parser, succeeds. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING FOR word, word; +-- No mapping for token supported by the configuration's parser, fails. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING FOR word; +ERROR: mapping for token type "word" does not exist +-- Token supported by the configuration's parser, cannot be found, +-- succeeds with IF EXISTS. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING IF EXISTS FOR word, word; +NOTICE: mapping for token type "word" does not exist, skipping +-- Re-add mapping, with duplicated tokens supported by the parser. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + ADD MAPPING FOR word, word WITH ispell; +-- Not a token supported by the configuration's parser, fails. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + ADD MAPPING FOR not_a_token WITH ispell; +ERROR: token type "not_a_token" does not exist +DROP TEXT SEARCH CONFIGURATION dummy_tst; diff -Nru postgresql-13-13.13/src/test/regress/pg_regress.c postgresql-13-13.14/src/test/regress/pg_regress.c --- postgresql-13-13.13/src/test/regress/pg_regress.c 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/pg_regress.c 2024-02-05 21:47:02.000000000 +0000 @@ -1233,7 +1233,7 @@ comspec = "CMD"; memset(&pi, 0, sizeof(pi)); - cmdline2 = psprintf("\"%s\" /c \"%s\"", comspec, cmdline); + cmdline2 = psprintf("\"%s\" /d /c \"%s\"", comspec, cmdline); if ((restrictedToken = CreateRestrictedProcess(cmdline2, &pi)) == 0) diff -Nru postgresql-13-13.13/src/test/regress/sql/fast_default.sql postgresql-13-13.14/src/test/regress/sql/fast_default.sql --- postgresql-13-13.13/src/test/regress/sql/fast_default.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/fast_default.sql 2024-02-05 21:47:02.000000000 +0000 @@ -256,7 +256,18 @@ SELECT comp(); +-- check that we notice insertion of a volatile default argument +CREATE FUNCTION foolme(timestamptz DEFAULT clock_timestamp()) + RETURNS timestamptz + IMMUTABLE AS 'select $1' LANGUAGE sql; +ALTER TABLE T ADD COLUMN c3 timestamptz DEFAULT foolme(); + +SELECT attname, atthasmissing, attmissingval FROM pg_attribute + WHERE attrelid = 't'::regclass AND attnum > 0 + ORDER BY attnum; + DROP TABLE T; +DROP FUNCTION foolme(timestamptz); -- Simple querie CREATE TABLE T (pk INT NOT NULL PRIMARY KEY); diff -Nru postgresql-13-13.13/src/test/regress/sql/generated.sql postgresql-13-13.14/src/test/regress/sql/generated.sql --- postgresql-13-13.13/src/test/regress/sql/generated.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/generated.sql 2024-02-05 21:47:02.000000000 +0000 @@ -26,6 +26,9 @@ -- generation expression must be immutable CREATE TABLE gtest_err_4 (a int PRIMARY KEY, b double precision GENERATED ALWAYS AS (random()) STORED); +-- ... but be sure that the immutability test is accurate +CREATE TABLE gtest2 (a int, b text GENERATED ALWAYS AS (a || ' sec') STORED); +DROP TABLE gtest2; -- cannot have default/identity and generated CREATE TABLE gtest_err_5a (a int PRIMARY KEY, b int DEFAULT 5 GENERATED ALWAYS AS (a * 2) STORED); diff -Nru postgresql-13-13.13/src/test/regress/sql/horology.sql postgresql-13-13.14/src/test/regress/sql/horology.sql --- postgresql-13-13.13/src/test/regress/sql/horology.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/horology.sql 2024-02-05 21:47:02.000000000 +0000 @@ -86,6 +86,7 @@ SELECT timestamp without time zone 'Jan 1, 4713 BC' + interval '106000000 days' AS "Feb 23, 285506"; SELECT timestamp without time zone 'Jan 1, 4713 BC' + interval '107000000 days' AS "Jan 20, 288244"; SELECT timestamp without time zone 'Jan 1, 4713 BC' + interval '109203489 days' AS "Dec 31, 294276"; +SELECT timestamp without time zone '2000-01-01' - interval '2483590 days' AS "out of range"; SELECT timestamp without time zone '12/31/294276' - timestamp without time zone '12/23/1999' AS "106751991 Days"; -- Shorthand values @@ -117,6 +118,7 @@ SELECT timestamp with time zone '1999-03-01' - interval '1 second' AS "Feb 28"; SELECT timestamp with time zone '2000-03-01' - interval '1 second' AS "Feb 29"; SELECT timestamp with time zone '1999-12-01' + interval '1 month - 1 second' AS "Dec 31"; +SELECT timestamp with time zone '2000-01-01' - interval '2483590 days' AS "out of range"; SELECT (timestamp with time zone 'today' = (timestamp with time zone 'yesterday' + interval '1 day')) as "True"; SELECT (timestamp with time zone 'today' = (timestamp with time zone 'tomorrow' - interval '1 day')) as "True"; diff -Nru postgresql-13-13.13/src/test/regress/sql/indexing.sql postgresql-13-13.14/src/test/regress/sql/indexing.sql --- postgresql-13-13.13/src/test/regress/sql/indexing.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/indexing.sql 2024-02-05 21:47:02.000000000 +0000 @@ -668,6 +668,26 @@ select tableoid::regclass, * from idxpart order by a; drop table idxpart; +-- Test some other non-btree index types +create table idxpart (a int, b text, c int[]) partition by range (a); +create table idxpart1 partition of idxpart for values from (0) to (100000); +set enable_seqscan to off; + +create index idxpart_brin on idxpart using brin(b); +explain (costs off) select * from idxpart where b = 'abcd'; +drop index idxpart_brin; + +create index idxpart_spgist on idxpart using spgist(b); +explain (costs off) select * from idxpart where b = 'abcd'; +drop index idxpart_spgist; + +create index idxpart_gin on idxpart using gin(c); +explain (costs off) select * from idxpart where c @> array[42]; +drop index idxpart_gin; + +reset enable_seqscan; +drop table idxpart; + -- intentionally leave some objects around create table idxpart (a int) partition by range (a); create table idxpart1 partition of idxpart for values from (0) to (100); diff -Nru postgresql-13-13.13/src/test/regress/sql/inherit.sql postgresql-13-13.14/src/test/regress/sql/inherit.sql --- postgresql-13-13.13/src/test/regress/sql/inherit.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/inherit.sql 2024-02-05 21:47:02.000000000 +0000 @@ -353,6 +353,15 @@ DROP TABLE inhts; +-- Test for adding a column to a parent table with complex inheritance +CREATE TABLE inhta (); +CREATE TABLE inhtb () INHERITS (inhta); +CREATE TABLE inhtc () INHERITS (inhtb); +CREATE TABLE inhtd () INHERITS (inhta, inhtb, inhtc); +ALTER TABLE inhta ADD COLUMN i int; +\d+ inhta +DROP TABLE inhta, inhtb, inhtc, inhtd; + -- Test for renaming in diamond inheritance CREATE TABLE inht2 (x int) INHERITS (inht1); CREATE TABLE inht3 (y int) INHERITS (inht1); diff -Nru postgresql-13-13.13/src/test/regress/sql/int8.sql postgresql-13-13.14/src/test/regress/sql/int8.sql --- postgresql-13-13.13/src/test/regress/sql/int8.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/int8.sql 2024-02-05 21:47:02.000000000 +0000 @@ -131,6 +131,7 @@ select -('-9223372036854775807'::int8); select -('-9223372036854775808'::int8); +select 0::int8 - '-9223372036854775808'::int8; select '9223372036854775800'::int8 + '9223372036854775800'::int8; select '-9223372036854775800'::int8 + '-9223372036854775800'::int8; diff -Nru postgresql-13-13.13/src/test/regress/sql/interval.sql postgresql-13-13.14/src/test/regress/sql/interval.sql --- postgresql-13-13.13/src/test/regress/sql/interval.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/interval.sql 2024-02-05 21:47:02.000000000 +0000 @@ -129,6 +129,14 @@ SELECT '' AS ten, * FROM INTERVAL_TBL; +-- multiplication and division overflow test cases +SELECT '3000000 months'::interval * 1000; +SELECT '3000000 months'::interval / 0.001; +SELECT '3000000 days'::interval * 1000; +SELECT '3000000 days'::interval / 0.001; +SELECT '1 month 2146410 days'::interval * 1000.5002; +SELECT make_interval(0, 0, 0, 0, 0, 0, 4611686018427.387904) / 0.1; + -- test avg(interval), which is somewhat fragile since people have been -- known to change the allowed input syntax for type interval without -- updating pg_aggregate.agginitval diff -Nru postgresql-13-13.13/src/test/regress/sql/join.sql postgresql-13-13.14/src/test/regress/sql/join.sql --- postgresql-13-13.13/src/test/regress/sql/join.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/join.sql 2024-02-05 21:47:02.000000000 +0000 @@ -1948,6 +1948,18 @@ ) on c.q2 = ss2.q1, lateral (select ss2.y offset 0) ss3; +-- another case requiring nested PlaceHolderVars +explain (verbose, costs off) +select * from + (select 0 as val0) as ss0 + left join (select 1 as val) as ss1 on true + left join lateral (select ss1.val as val_filtered where false) as ss2 on true; + +select * from + (select 0 as val0) as ss0 + left join (select 1 as val) as ss1 on true + left join lateral (select ss1.val as val_filtered where false) as ss2 on true; + -- case that breaks the old ph_may_need optimization explain (verbose, costs off) select c.*,a.*,ss1.q1,ss2.q1,ss3.* from diff -Nru postgresql-13-13.13/src/test/regress/sql/matview.sql postgresql-13-13.14/src/test/regress/sql/matview.sql --- postgresql-13-13.13/src/test/regress/sql/matview.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/matview.sql 2024-02-05 21:47:02.000000000 +0000 @@ -231,6 +231,23 @@ DROP OWNED BY regress_user_mvtest CASCADE; DROP ROLE regress_user_mvtest; +-- Concurrent refresh requires a unique index on the materialized +-- view. Test what happens if it's dropped during the refresh. +CREATE OR REPLACE FUNCTION mvtest_drop_the_index() + RETURNS bool AS $$ +BEGIN + EXECUTE 'DROP INDEX IF EXISTS mvtest_drop_idx'; + RETURN true; +END; +$$ LANGUAGE plpgsql; + +CREATE MATERIALIZED VIEW drop_idx_matview AS + SELECT 1 as i WHERE mvtest_drop_the_index(); + +CREATE UNIQUE INDEX mvtest_drop_idx ON drop_idx_matview (i); +REFRESH MATERIALIZED VIEW CONCURRENTLY drop_idx_matview; +DROP MATERIALIZED VIEW drop_idx_matview; -- clean up + -- make sure that create WITH NO DATA works via SPI BEGIN; CREATE FUNCTION mvtest_func() diff -Nru postgresql-13-13.13/src/test/regress/sql/opr_sanity.sql postgresql-13-13.14/src/test/regress/sql/opr_sanity.sql --- postgresql-13-13.13/src/test/regress/sql/opr_sanity.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/opr_sanity.sql 2024-02-05 21:47:02.000000000 +0000 @@ -1244,7 +1244,7 @@ SELECT p1.oid, p1.amname, p2.oid, p2.proname FROM pg_am AS p1, pg_proc AS p2 -WHERE p2.oid = p1.amhandler AND p1.amtype = 's' AND +WHERE p2.oid = p1.amhandler AND p1.amtype = 't' AND (p2.prorettype != 'table_am_handler'::regtype OR p2.proretset OR p2.pronargs != 1 diff -Nru postgresql-13-13.13/src/test/regress/sql/partition_join.sql postgresql-13-13.14/src/test/regress/sql/partition_join.sql --- postgresql-13-13.13/src/test/regress/sql/partition_join.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/partition_join.sql 2024-02-05 21:47:02.000000000 +0000 @@ -91,6 +91,33 @@ (SELECT t2.a AS t2a, t3.a AS t3a, t2.b t2b, t2.c t2c, least(t1.a,t2.a,t3.a) FROM prt1 t2 JOIN prt2 t3 ON (t2.a = t3.b)) ss ON t1.c = ss.t2c WHERE (t1.b + coalesce(ss.t2b, 0)) = 0 ORDER BY t1.a; +SET max_parallel_workers_per_gather = 0; +-- If there are lateral references to the other relation in sample scan, +-- we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT * FROM prt1 t1 JOIN LATERAL + (SELECT * FROM prt1 t2 TABLESAMPLE SYSTEM (t1.a) REPEATABLE(t1.b)) s + ON t1.a = s.a; + +-- If there are lateral references to the other relation in scan's restriction +-- clauses, we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.a; +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.a; + +EXPLAIN (COSTS OFF) +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.b; +SELECT count(*) FROM prt1 t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2 t2) s + ON t1.a = s.b WHERE s.t1b = s.b; +RESET max_parallel_workers_per_gather; + -- bug with inadequate sort key representation SET enable_partitionwise_aggregate TO true; SET enable_hashjoin TO false; @@ -378,6 +405,27 @@ (SELECT t2.a AS t2a, t2.c AS t2c, t2.b AS t2b, t3.b AS t3b, least(t1.a,t2.a,t3.b) FROM prt1_l t2 JOIN prt2_l t3 ON (t2.a = t3.b AND t2.c = t3.c)) ss ON t1.a = ss.t2a AND t1.c = ss.t2c WHERE t1.b = 0 ORDER BY t1.a; +SET max_parallel_workers_per_gather = 0; +-- If there are lateral references to the other relation in sample scan, +-- we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT * FROM prt1_l t1 JOIN LATERAL + (SELECT * FROM prt1_l t2 TABLESAMPLE SYSTEM (t1.a) REPEATABLE(t1.b)) s + ON t1.a = s.a AND t1.b = s.b AND t1.c = s.c; + +-- If there are lateral references to the other relation in scan's restriction +-- clauses, we cannot generate a partitionwise join. +EXPLAIN (COSTS OFF) +SELECT COUNT(*) FROM prt1_l t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2_l t2) s + ON t1.a = s.b AND t1.b = s.a AND t1.c = s.c + WHERE s.t1b = s.a; +SELECT COUNT(*) FROM prt1_l t1 LEFT JOIN LATERAL + (SELECT t1.b AS t1b, t2.* FROM prt2_l t2) s + ON t1.a = s.b AND t1.b = s.a AND t1.c = s.c + WHERE s.t1b = s.a; +RESET max_parallel_workers_per_gather; + -- join with one side empty EXPLAIN (COSTS OFF) SELECT t1.a, t1.c, t2.b, t2.c FROM (SELECT * FROM prt1_l WHERE a = 1 AND a = 2) t1 RIGHT JOIN prt2_l t2 ON t1.a = t2.b AND t1.b = t2.a AND t1.c = t2.c; diff -Nru postgresql-13-13.13/src/test/regress/sql/tsdicts.sql postgresql-13-13.14/src/test/regress/sql/tsdicts.sql --- postgresql-13-13.13/src/test/regress/sql/tsdicts.sql 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/test/regress/sql/tsdicts.sql 2024-02-05 21:47:02.000000000 +0000 @@ -251,3 +251,33 @@ "DictFile" = ispell_sample, "AffFile" = ispell_sample ); + +-- Test grammar for configurations +CREATE TEXT SEARCH CONFIGURATION dummy_tst (COPY=english); +-- Overriden mapping change with duplicated tokens. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + ALTER MAPPING FOR word, word WITH ispell; +-- Not a token supported by the configuration's parser, fails. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING FOR not_a_token, not_a_token; +-- Not a token supported by the configuration's parser, fails even +-- with IF EXISTS. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING IF EXISTS FOR not_a_token, not_a_token; +-- Token supported by the configuration's parser, succeeds. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING FOR word, word; +-- No mapping for token supported by the configuration's parser, fails. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING FOR word; +-- Token supported by the configuration's parser, cannot be found, +-- succeeds with IF EXISTS. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + DROP MAPPING IF EXISTS FOR word, word; +-- Re-add mapping, with duplicated tokens supported by the parser. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + ADD MAPPING FOR word, word WITH ispell; +-- Not a token supported by the configuration's parser, fails. +ALTER TEXT SEARCH CONFIGURATION dummy_tst + ADD MAPPING FOR not_a_token WITH ispell; +DROP TEXT SEARCH CONFIGURATION dummy_tst; diff -Nru postgresql-13-13.13/src/timezone/data/tzdata.zi postgresql-13-13.14/src/timezone/data/tzdata.zi --- postgresql-13-13.13/src/timezone/data/tzdata.zi 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/timezone/data/tzdata.zi 2024-02-05 21:47:02.000000000 +0000 @@ -1,4 +1,4 @@ -# version 2023c +# version 2024a # This zic input file is in the public domain. R d 1916 o - Jun 14 23s 1 S R d 1916 1919 - O Su>=1 23s 0 - @@ -22,27 +22,6 @@ R d 1978 o - S 22 3 0 - R d 1980 o - Ap 25 0 1 S R d 1980 o - O 31 2 0 - -Z Africa/Algiers 0:12:12 - LMT 1891 Mar 16 -0:9:21 - PMT 1911 Mar 11 -0 d WE%sT 1940 F 25 2 -1 d CE%sT 1946 O 7 -0 - WET 1956 Ja 29 -1 - CET 1963 Ap 14 -0 d WE%sT 1977 O 21 -1 d CE%sT 1979 O 26 -0 d WE%sT 1981 May -1 - CET -Z Atlantic/Cape_Verde -1:34:4 - LMT 1912 Ja 1 2u --2 - -02 1942 S --2 1 -01 1945 O 15 --2 - -02 1975 N 25 2 --1 - -01 -Z Africa/Ndjamena 1:0:12 - LMT 1912 -1 - WAT 1979 O 14 -1 1 WAST 1980 Mar 8 -1 - WAT -Z Africa/Abidjan -0:16:8 - LMT 1912 -0 - GMT R K 1940 o - Jul 15 0 1 S R K 1940 o - O 1 0 0 - R K 1941 o - Ap 15 0 1 S @@ -77,21 +56,6 @@ R K 2014 o - S lastTh 24 0 - R K 2023 ma - Ap lastF 0 1 S R K 2023 ma - O lastTh 24 0 - -Z Africa/Cairo 2:5:9 - LMT 1900 O -2 K EE%sT -Z Africa/Bissau -1:2:20 - LMT 1912 Ja 1 1u --1 - -01 1975 -0 - GMT -Z Africa/Nairobi 2:27:16 - LMT 1908 May -2:30 - +0230 1928 Jun 30 24 -3 - EAT 1930 Ja 4 24 -2:30 - +0230 1936 D 31 24 -2:45 - +0245 1942 Jul 31 24 -3 - EAT -Z Africa/Monrovia -0:43:8 - LMT 1882 --0:43:8 - MMT 1919 Mar --0:44:30 - MMT 1972 Ja 7 -0 - GMT R L 1951 o - O 14 2 1 S R L 1952 o - Ja 1 0 0 - R L 1953 o - O 9 2 1 S @@ -109,21 +73,10 @@ R L 1997 o - O 4 0 0 - R L 2013 o - Mar lastF 1 1 S R L 2013 o - O lastF 2 0 - -Z Africa/Tripoli 0:52:44 - LMT 1920 -1 L CE%sT 1959 -2 - EET 1982 -1 L CE%sT 1990 May 4 -2 - EET 1996 S 30 -1 L CE%sT 1997 O 4 -2 - EET 2012 N 10 2 -1 L CE%sT 2013 O 25 2 -2 - EET R MU 1982 o - O 10 0 1 - R MU 1983 o - Mar 21 0 0 - R MU 2008 o - O lastSu 2 1 - R MU 2009 o - Mar lastSu 2 0 - -Z Indian/Mauritius 3:50 - LMT 1907 -4 MU +04/+05 R M 1939 o - S 12 0 1 - R M 1939 o - N 19 0 0 - R M 1940 o - F 25 0 1 - @@ -307,53 +260,15 @@ R M 2086 o - May 19 2 0 - R M 2087 o - Mar 30 3 -1 - R M 2087 o - May 11 2 0 - -Z Africa/Casablanca -0:30:20 - LMT 1913 O 26 -0 M +00/+01 1984 Mar 16 -1 - +01 1986 -0 M +00/+01 2018 O 28 3 -1 M +01/+00 -Z Africa/El_Aaiun -0:52:48 - LMT 1934 --1 - -01 1976 Ap 14 -0 M +00/+01 2018 O 28 3 -1 M +01/+00 -Z Africa/Maputo 2:10:20 - LMT 1903 Mar -2 - CAT R NA 1994 o - Mar 21 0 -1 WAT R NA 1994 2017 - S Su>=1 2 0 CAT R NA 1995 2017 - Ap Su>=1 2 -1 WAT -Z Africa/Windhoek 1:8:24 - LMT 1892 F 8 -1:30 - +0130 1903 Mar -2 - SAST 1942 S 20 2 -2 1 SAST 1943 Mar 21 2 -2 - SAST 1990 Mar 21 -2 NA %s -Z Africa/Lagos 0:13:35 - LMT 1905 Jul -0 - GMT 1908 Jul -0:13:35 - LMT 1914 -0:30 - +0030 1919 S -1 - WAT -Z Africa/Sao_Tome 0:26:56 - LMT 1884 --0:36:45 - LMT 1912 Ja 1 0u -0 - GMT 2018 Ja 1 1 -1 - WAT 2019 Ja 1 2 -0 - GMT R SA 1942 1943 - S Su>=15 2 1 - R SA 1943 1944 - Mar Su>=15 2 0 - -Z Africa/Johannesburg 1:52 - LMT 1892 F 8 -1:30 - SAST 1903 Mar -2 SA SAST R SD 1970 o - May 1 0 1 S R SD 1970 1985 - O 15 0 0 - R SD 1971 o - Ap 30 0 1 S R SD 1972 1985 - Ap lastSu 0 1 S -Z Africa/Khartoum 2:10:8 - LMT 1931 -2 SD CA%sT 2000 Ja 15 12 -3 - EAT 2017 N -2 - CAT -Z Africa/Juba 2:6:28 - LMT 1931 -2 SD CA%sT 2000 Ja 15 12 -3 - EAT 2021 F -2 - CAT R n 1939 o - Ap 15 23s 1 S R n 1939 o - N 18 23s 0 - R n 1940 o - F 25 23s 1 S @@ -379,80 +294,14 @@ R n 2005 o - S 30 1s 0 - R n 2006 2008 - Mar lastSu 2s 1 S R n 2006 2008 - O lastSu 2s 0 - -Z Africa/Tunis 0:40:44 - LMT 1881 May 12 -0:9:21 - PMT 1911 Mar 11 -1 n CE%sT -Z Antarctica/Casey 0 - -00 1969 -8 - +08 2009 O 18 2 -11 - +11 2010 Mar 5 2 -8 - +08 2011 O 28 2 -11 - +11 2012 F 21 17u -8 - +08 2016 O 22 -11 - +11 2018 Mar 11 4 -8 - +08 2018 O 7 4 -11 - +11 2019 Mar 17 3 -8 - +08 2019 O 4 3 -11 - +11 2020 Mar 8 3 -8 - +08 2020 O 4 0:1 -11 - +11 -Z Antarctica/Davis 0 - -00 1957 Ja 13 -7 - +07 1964 N -0 - -00 1969 F -7 - +07 2009 O 18 2 -5 - +05 2010 Mar 10 20u -7 - +07 2011 O 28 2 -5 - +05 2012 F 21 20u -7 - +07 -Z Antarctica/Mawson 0 - -00 1954 F 13 -6 - +06 2009 O 18 2 -5 - +05 R Tr 2005 ma - Mar lastSu 1u 2 +02 R Tr 2004 ma - O lastSu 1u 0 +00 -Z Antarctica/Troll 0 - -00 2005 F 12 -0 Tr %s -Z Antarctica/Rothera 0 - -00 1976 D --3 - -03 -Z Asia/Kabul 4:36:48 - LMT 1890 -4 - +04 1945 -4:30 - +0430 R AM 2011 o - Mar lastSu 2s 1 - R AM 2011 o - O lastSu 2s 0 - -Z Asia/Yerevan 2:58 - LMT 1924 May 2 -3 - +03 1957 Mar -4 R +04/+05 1991 Mar 31 2s -3 R +03/+04 1995 S 24 2s -4 - +04 1997 -4 R +04/+05 2011 -4 AM +04/+05 R AZ 1997 2015 - Mar lastSu 4 1 - R AZ 1997 2015 - O lastSu 5 0 - -Z Asia/Baku 3:19:24 - LMT 1924 May 2 -3 - +03 1957 Mar -4 R +04/+05 1991 Mar 31 2s -3 R +03/+04 1992 S lastSu 2s -4 - +04 1996 -4 E +04/+05 1997 -4 AZ +04/+05 R BD 2009 o - Jun 19 23 1 - R BD 2009 o - D 31 24 0 - -Z Asia/Dhaka 6:1:40 - LMT 1890 -5:53:20 - HMT 1941 O -6:30 - +0630 1942 May 15 -5:30 - +0530 1942 S -6:30 - +0630 1951 S 30 -6 - +06 2009 -6 BD +06/+07 -Z Asia/Thimphu 5:58:36 - LMT 1947 Au 15 -5:30 - +0530 1987 O -6 - +06 -Z Indian/Chagos 4:49:40 - LMT 1907 -5 - +05 1996 -6 - +06 -Z Asia/Yangon 6:24:47 - LMT 1880 -6:24:47 - RMT 1920 -6:30 - +0630 1942 May -9 - +09 1945 May 3 -6:30 - +0630 R Sh 1919 o - Ap 12 24 1 D R Sh 1919 o - S 30 24 0 S R Sh 1940 o - Jun 1 0 1 D @@ -470,11 +319,6 @@ R CN 1986 o - May 4 2 1 D R CN 1986 1991 - S Su>=11 2 0 S R CN 1987 1991 - Ap Su>=11 2 1 D -Z Asia/Shanghai 8:5:43 - LMT 1901 -8 Sh C%sT 1949 May 28 -8 CN C%sT -Z Asia/Urumqi 5:50:20 - LMT 1928 -6 - +06 R HK 1946 o - Ap 21 0 1 S R HK 1946 o - D 1 3:30s 0 - R HK 1947 o - Ap 13 3:30s 1 S @@ -489,12 +333,6 @@ R HK 1973 o - D 30 3:30 1 S R HK 1979 o - May 13 3:30 1 S R HK 1979 o - O 21 3:30 0 - -Z Asia/Hong_Kong 7:36:42 - LMT 1904 O 29 17u -8 - HKT 1941 Jun 15 3 -8 1 HKST 1941 O 1 4 -8 0:30 HKWT 1941 D 25 -9 - JST 1945 N 18 2 -8 HK HK%sT R f 1946 o - May 15 0 1 D R f 1946 o - O 1 0 0 S R f 1947 o - Ap 15 0 1 D @@ -510,10 +348,6 @@ R f 1974 1975 - O 1 0 0 S R f 1979 o - Jul 1 0 1 D R f 1979 o - O 1 0 0 S -Z Asia/Taipei 8:6 - LMT 1896 -8 - CST 1937 O -9 - JST 1945 S 21 1 -8 f C%sT R _ 1942 1943 - Ap 30 23 1 - R _ 1942 o - N 17 23 0 - R _ 1943 o - S 30 23 0 S @@ -541,10 +375,6 @@ R _ 1975 1976 - Ap Su>=16 3:30 1 D R _ 1979 o - May 13 3:30 1 D R _ 1979 o - O Su>=16 3:30 0 S -Z Asia/Macau 7:34:10 - LMT 1904 O 30 -8 - CST 1941 D 21 23 -9 _ +09/+10 1945 S 30 24 -8 _ C%sT R CY 1975 o - Ap 13 0 1 S R CY 1975 o - O 12 0 0 - R CY 1976 o - May 15 0 1 S @@ -554,65 +384,6 @@ R CY 1978 o - O 2 0 0 - R CY 1979 1997 - S lastSu 0 0 - R CY 1981 1998 - Mar lastSu 0 1 S -Z Asia/Nicosia 2:13:28 - LMT 1921 N 14 -2 CY EE%sT 1998 S -2 E EE%sT -Z Asia/Famagusta 2:15:48 - LMT 1921 N 14 -2 CY EE%sT 1998 S -2 E EE%sT 2016 S 8 -3 - +03 2017 O 29 1u -2 E EE%sT -Z Asia/Tbilisi 2:59:11 - LMT 1880 -2:59:11 - TBMT 1924 May 2 -3 - +03 1957 Mar -4 R +04/+05 1991 Mar 31 2s -3 R +03/+04 1992 -3 e +03/+04 1994 S lastSu -4 e +04/+05 1996 O lastSu -4 1 +05 1997 Mar lastSu -4 e +04/+05 2004 Jun 27 -3 R +03/+04 2005 Mar lastSu 2 -4 - +04 -Z Asia/Dili 8:22:20 - LMT 1912 -8 - +08 1942 F 21 23 -9 - +09 1976 May 3 -8 - +08 2000 S 17 -9 - +09 -Z Asia/Kolkata 5:53:28 - LMT 1854 Jun 28 -5:53:20 - HMT 1870 -5:21:10 - MMT 1906 -5:30 - IST 1941 O -5:30 1 +0630 1942 May 15 -5:30 - IST 1942 S -5:30 1 +0630 1945 O 15 -5:30 - IST -Z Asia/Jakarta 7:7:12 - LMT 1867 Au 10 -7:7:12 - BMT 1923 D 31 16:40u -7:20 - +0720 1932 N -7:30 - +0730 1942 Mar 23 -9 - +09 1945 S 23 -7:30 - +0730 1948 May -8 - +08 1950 May -7:30 - +0730 1964 -7 - WIB -Z Asia/Pontianak 7:17:20 - LMT 1908 May -7:17:20 - PMT 1932 N -7:30 - +0730 1942 Ja 29 -9 - +09 1945 S 23 -7:30 - +0730 1948 May -8 - +08 1950 May -7:30 - +0730 1964 -8 - WITA 1988 -7 - WIB -Z Asia/Makassar 7:57:36 - LMT 1920 -7:57:36 - MMT 1932 N -8 - +08 1942 F 9 -9 - +09 1945 S 23 -8 - WITA -Z Asia/Jayapura 9:22:48 - LMT 1932 N -9 - +09 1944 S -9:30 - +0930 1964 -9 - WIT R i 1910 o - Ja 1 0 0 - R i 1977 o - Mar 21 23 1 - R i 1977 o - O 20 24 0 - @@ -653,11 +424,6 @@ R i 2020 o - S 20 24 0 - R i 2021 2022 - Mar 21 24 1 - R i 2021 2022 - S 21 24 0 - -Z Asia/Tehran 3:25:44 - LMT 1916 -3:25:44 - TMT 1935 Jun 13 -3:30 i +0330/+0430 1977 O 20 24 -4 i +04/+05 1979 -3:30 i +0330/+0430 R IQ 1982 o - May 1 0 1 - R IQ 1982 1984 - O 1 0 0 - R IQ 1983 o - Mar 31 0 1 - @@ -666,10 +432,6 @@ R IQ 1986 1990 - Mar lastSu 1s 1 - R IQ 1991 2007 - Ap 1 3s 1 - R IQ 1991 2007 - O 1 3s 0 - -Z Asia/Baghdad 2:57:40 - LMT 1890 -2:57:36 - BMT 1918 -3 - +03 1982 May -3 IQ +03/+04 R Z 1940 o - May 31 24u 1 D R Z 1940 o - S 30 24u 0 S R Z 1940 o - N 16 24u 1 D @@ -755,15 +517,10 @@ R Z 2012 o - S 23 2 0 S R Z 2013 ma - Mar F>=23 2 1 D R Z 2013 ma - O lastSu 2 0 S -Z Asia/Jerusalem 2:20:54 - LMT 1880 -2:20:40 - JMT 1918 -2 Z I%sT R JP 1948 o - May Sa>=1 24 1 D R JP 1948 1951 - S Sa>=8 25 0 S R JP 1949 o - Ap Sa>=1 24 1 D R JP 1950 1951 - May Sa>=1 24 1 D -Z Asia/Tokyo 9:18:59 - LMT 1887 D 31 15u -9 JP J%sT R J 1973 o - Jun 6 0 1 S R J 1973 1975 - O 1 0 0 - R J 1974 1977 - May 1 0 1 S @@ -796,83 +553,10 @@ R J 2014 2021 - Mar lastTh 24 1 S R J 2014 2022 - O lastF 0s 0 - R J 2022 o - F lastTh 24 1 S -Z Asia/Amman 2:23:44 - LMT 1931 -2 J EE%sT 2022 O 28 0s -3 - +03 -Z Asia/Almaty 5:7:48 - LMT 1924 May 2 -5 - +05 1930 Jun 21 -6 R +06/+07 1991 Mar 31 2s -5 R +05/+06 1992 Ja 19 2s -6 R +06/+07 2004 O 31 2s -6 - +06 -Z Asia/Qyzylorda 4:21:52 - LMT 1924 May 2 -4 - +04 1930 Jun 21 -5 - +05 1981 Ap -5 1 +06 1981 O -6 - +06 1982 Ap -5 R +05/+06 1991 Mar 31 2s -4 R +04/+05 1991 S 29 2s -5 R +05/+06 1992 Ja 19 2s -6 R +06/+07 1992 Mar 29 2s -5 R +05/+06 2004 O 31 2s -6 - +06 2018 D 21 -5 - +05 -Z Asia/Qostanay 4:14:28 - LMT 1924 May 2 -4 - +04 1930 Jun 21 -5 - +05 1981 Ap -5 1 +06 1981 O -6 - +06 1982 Ap -5 R +05/+06 1991 Mar 31 2s -4 R +04/+05 1992 Ja 19 2s -5 R +05/+06 2004 O 31 2s -6 - +06 -Z Asia/Aqtobe 3:48:40 - LMT 1924 May 2 -4 - +04 1930 Jun 21 -5 - +05 1981 Ap -5 1 +06 1981 O -6 - +06 1982 Ap -5 R +05/+06 1991 Mar 31 2s -4 R +04/+05 1992 Ja 19 2s -5 R +05/+06 2004 O 31 2s -5 - +05 -Z Asia/Aqtau 3:21:4 - LMT 1924 May 2 -4 - +04 1930 Jun 21 -5 - +05 1981 O -6 - +06 1982 Ap -5 R +05/+06 1991 Mar 31 2s -4 R +04/+05 1992 Ja 19 2s -5 R +05/+06 1994 S 25 2s -4 R +04/+05 2004 O 31 2s -5 - +05 -Z Asia/Atyrau 3:27:44 - LMT 1924 May 2 -3 - +03 1930 Jun 21 -5 - +05 1981 O -6 - +06 1982 Ap -5 R +05/+06 1991 Mar 31 2s -4 R +04/+05 1992 Ja 19 2s -5 R +05/+06 1999 Mar 28 2s -4 R +04/+05 2004 O 31 2s -5 - +05 -Z Asia/Oral 3:25:24 - LMT 1924 May 2 -3 - +03 1930 Jun 21 -5 - +05 1981 Ap -5 1 +06 1981 O -6 - +06 1982 Ap -5 R +05/+06 1989 Mar 26 2s -4 R +04/+05 1992 Ja 19 2s -5 R +05/+06 1992 Mar 29 2s -4 R +04/+05 2004 O 31 2s -5 - +05 R KG 1992 1996 - Ap Su>=7 0s 1 - R KG 1992 1996 - S lastSu 0 0 - R KG 1997 2005 - Mar lastSu 2:30 1 - R KG 1997 2004 - O lastSu 2:30 0 - -Z Asia/Bishkek 4:58:24 - LMT 1924 May 2 -5 - +05 1930 Jun 21 -6 R +06/+07 1991 Mar 31 2s -5 R +05/+06 1991 Au 31 2 -5 KG +05/+06 2005 Au 12 -6 - +06 R KR 1948 o - Jun 1 0 1 D R KR 1948 o - S 12 24 0 S R KR 1949 o - Ap 3 0 1 D @@ -887,18 +571,6 @@ R KR 1957 1960 - S Sa>=17 24 0 S R KR 1987 1988 - May Su>=8 2 1 D R KR 1987 1988 - O Su>=8 3 0 S -Z Asia/Seoul 8:27:52 - LMT 1908 Ap -8:30 - KST 1912 -9 - JST 1945 S 8 -9 KR K%sT 1954 Mar 21 -8:30 KR K%sT 1961 Au 10 -9 KR K%sT -Z Asia/Pyongyang 8:23 - LMT 1908 Ap -8:30 - KST 1912 -9 - JST 1945 Au 24 -9 - KST 2015 Au 15 -8:30 - KST 2018 May 4 23:30 -9 - KST R l 1920 o - Mar 28 0 1 S R l 1920 o - O 25 0 0 - R l 1921 o - Ap 3 0 1 S @@ -923,18 +595,8 @@ R l 1993 ma - Mar lastSu 0 1 S R l 1993 1998 - S lastSu 0 0 - R l 1999 ma - O lastSu 0 0 - -Z Asia/Beirut 2:22 - LMT 1880 -2 l EE%sT R NB 1935 1941 - S 14 0 0:20 - R NB 1935 1941 - D 14 0 0 - -Z Asia/Kuching 7:21:20 - LMT 1926 Mar -7:30 - +0730 1933 -8 NB +08/+0820 1942 F 16 -9 - +09 1945 S 12 -8 - +08 -Z Indian/Maldives 4:54 - LMT 1880 -4:54 - MMT 1960 -5 - +05 R X 1983 1984 - Ap 1 0 1 - R X 1983 o - O 1 0 0 - R X 1985 1998 - Mar lastSu 0 1 - @@ -944,31 +606,11 @@ R X 2002 2006 - Mar lastSa 2 1 - R X 2015 2016 - Mar lastSa 2 1 - R X 2015 2016 - S lastSa 0 0 - -Z Asia/Hovd 6:6:36 - LMT 1905 Au -6 - +06 1978 -7 X +07/+08 -Z Asia/Ulaanbaatar 7:7:32 - LMT 1905 Au -7 - +07 1978 -8 X +08/+09 -Z Asia/Choibalsan 7:38 - LMT 1905 Au -7 - +07 1978 -8 - +08 1983 Ap -9 X +09/+10 2008 Mar 31 -8 X +08/+09 -Z Asia/Kathmandu 5:41:16 - LMT 1920 -5:30 - +0530 1986 -5:45 - +0545 R PK 2002 o - Ap Su>=2 0 1 S R PK 2002 o - O Su>=2 0 0 - R PK 2008 o - Jun 1 0 1 S R PK 2008 2009 - N 1 0 0 - R PK 2009 o - Ap 15 0 1 S -Z Asia/Karachi 4:28:12 - LMT 1907 -5:30 - +0530 1942 S -5:30 1 +0630 1945 O 15 -5:30 - +0530 1951 S 30 -5 - +05 1971 Mar 26 -5 PK PK%sT R P 1999 2005 - Ap F>=15 0 1 S R P 1999 2003 - O F>=15 0 0 - R P 2004 o - O 1 1 0 - @@ -1001,136 +643,90 @@ R P 2022 o - Mar 27 0 1 S R P 2022 2035 - O Sa<=30 2 0 - R P 2023 o - Ap 29 2 1 S -R P 2024 o - Ap 13 2 1 S -R P 2025 o - Ap 5 2 1 S +R P 2024 o - Ap 20 2 1 S +R P 2025 o - Ap 12 2 1 S R P 2026 2054 - Mar Sa<=30 2 1 S R P 2036 o - O 18 2 0 - R P 2037 o - O 10 2 0 - R P 2038 o - S 25 2 0 - R P 2039 o - S 17 2 0 - -R P 2039 o - O 22 2 1 S -R P 2039 2067 - O Sa<=30 2 0 - R P 2040 o - S 1 2 0 - -R P 2040 o - O 13 2 1 S +R P 2040 o - O 20 2 1 S +R P 2040 2067 - O Sa<=30 2 0 - R P 2041 o - Au 24 2 0 - -R P 2041 o - S 28 2 1 S +R P 2041 o - O 5 2 1 S R P 2042 o - Au 16 2 0 - -R P 2042 o - S 20 2 1 S +R P 2042 o - S 27 2 1 S R P 2043 o - Au 1 2 0 - -R P 2043 o - S 12 2 1 S +R P 2043 o - S 19 2 1 S R P 2044 o - Jul 23 2 0 - -R P 2044 o - Au 27 2 1 S +R P 2044 o - S 3 2 1 S R P 2045 o - Jul 15 2 0 - -R P 2045 o - Au 19 2 1 S +R P 2045 o - Au 26 2 1 S R P 2046 o - Jun 30 2 0 - -R P 2046 o - Au 11 2 1 S +R P 2046 o - Au 18 2 1 S R P 2047 o - Jun 22 2 0 - -R P 2047 o - Jul 27 2 1 S +R P 2047 o - Au 3 2 1 S R P 2048 o - Jun 6 2 0 - -R P 2048 o - Jul 18 2 1 S +R P 2048 o - Jul 25 2 1 S R P 2049 o - May 29 2 0 - -R P 2049 o - Jul 3 2 1 S +R P 2049 o - Jul 10 2 1 S R P 2050 o - May 21 2 0 - -R P 2050 o - Jun 25 2 1 S +R P 2050 o - Jul 2 2 1 S R P 2051 o - May 6 2 0 - -R P 2051 o - Jun 17 2 1 S +R P 2051 o - Jun 24 2 1 S R P 2052 o - Ap 27 2 0 - -R P 2052 o - Jun 1 2 1 S +R P 2052 o - Jun 8 2 1 S R P 2053 o - Ap 12 2 0 - -R P 2053 o - May 24 2 1 S +R P 2053 o - May 31 2 1 S R P 2054 o - Ap 4 2 0 - -R P 2054 o - May 16 2 1 S -R P 2055 o - May 1 2 1 S -R P 2056 o - Ap 22 2 1 S -R P 2057 o - Ap 7 2 1 S -R P 2058 ma - Mar Sa<=30 2 1 S +R P 2054 o - May 23 2 1 S +R P 2055 o - May 8 2 1 S +R P 2056 o - Ap 29 2 1 S +R P 2057 o - Ap 14 2 1 S +R P 2058 o - Ap 6 2 1 S +R P 2059 ma - Mar Sa<=30 2 1 S R P 2068 o - O 20 2 0 - R P 2069 o - O 12 2 0 - R P 2070 o - O 4 2 0 - R P 2071 o - S 19 2 0 - R P 2072 o - S 10 2 0 - -R P 2072 o - O 15 2 1 S +R P 2072 o - O 22 2 1 S +R P 2072 ma - O Sa<=30 2 0 - R P 2073 o - S 2 2 0 - -R P 2073 o - O 7 2 1 S +R P 2073 o - O 14 2 1 S R P 2074 o - Au 18 2 0 - -R P 2074 o - S 29 2 1 S +R P 2074 o - O 6 2 1 S R P 2075 o - Au 10 2 0 - -R P 2075 o - S 14 2 1 S -R P 2075 ma - O Sa<=30 2 0 - +R P 2075 o - S 21 2 1 S R P 2076 o - Jul 25 2 0 - -R P 2076 o - S 5 2 1 S +R P 2076 o - S 12 2 1 S R P 2077 o - Jul 17 2 0 - -R P 2077 o - Au 28 2 1 S +R P 2077 o - S 4 2 1 S R P 2078 o - Jul 9 2 0 - -R P 2078 o - Au 13 2 1 S +R P 2078 o - Au 20 2 1 S R P 2079 o - Jun 24 2 0 - -R P 2079 o - Au 5 2 1 S +R P 2079 o - Au 12 2 1 S R P 2080 o - Jun 15 2 0 - -R P 2080 o - Jul 20 2 1 S +R P 2080 o - Jul 27 2 1 S R P 2081 o - Jun 7 2 0 - -R P 2081 o - Jul 12 2 1 S +R P 2081 o - Jul 19 2 1 S R P 2082 o - May 23 2 0 - -R P 2082 o - Jul 4 2 1 S +R P 2082 o - Jul 11 2 1 S R P 2083 o - May 15 2 0 - -R P 2083 o - Jun 19 2 1 S +R P 2083 o - Jun 26 2 1 S R P 2084 o - Ap 29 2 0 - -R P 2084 o - Jun 10 2 1 S +R P 2084 o - Jun 17 2 1 S R P 2085 o - Ap 21 2 0 - -R P 2085 o - Jun 2 2 1 S +R P 2085 o - Jun 9 2 1 S R P 2086 o - Ap 13 2 0 - -R P 2086 o - May 18 2 1 S -Z Asia/Gaza 2:17:52 - LMT 1900 O -2 Z EET/EEST 1948 May 15 -2 K EE%sT 1967 Jun 5 -2 Z I%sT 1996 -2 J EE%sT 1999 -2 P EE%sT 2008 Au 29 -2 - EET 2008 S -2 P EE%sT 2010 -2 - EET 2010 Mar 27 0:1 -2 P EE%sT 2011 Au -2 - EET 2012 -2 P EE%sT -Z Asia/Hebron 2:20:23 - LMT 1900 O -2 Z EET/EEST 1948 May 15 -2 K EE%sT 1967 Jun 5 -2 Z I%sT 1996 -2 J EE%sT 1999 -2 P EE%sT +R P 2086 o - May 25 2 1 S R PH 1936 o - N 1 0 1 D R PH 1937 o - F 1 0 0 S R PH 1954 o - Ap 12 0 1 D R PH 1954 o - Jul 1 0 0 S R PH 1978 o - Mar 22 0 1 D R PH 1978 o - S 21 0 0 S -Z Asia/Manila -15:56 - LMT 1844 D 31 -8:4 - LMT 1899 May 11 -8 PH P%sT 1942 May -9 - JST 1944 N -8 PH P%sT -Z Asia/Qatar 3:26:8 - LMT 1920 -4 - +04 1972 Jun -3 - +03 -Z Asia/Riyadh 3:6:52 - LMT 1947 Mar 14 -3 - +03 -Z Asia/Singapore 6:55:25 - LMT 1901 -6:55:25 - SMT 1905 Jun -7 - +07 1933 -7 0:20 +0720 1936 -7:20 - +0720 1941 S -7:30 - +0730 1942 F 16 -9 - +09 1945 S 12 -7:30 - +0730 1981 D 31 16u -8 - +08 -Z Asia/Colombo 5:19:24 - LMT 1880 -5:19:32 - MMT 1906 -5:30 - +0530 1942 Ja 5 -5:30 0:30 +06 1942 S -5:30 1 +0630 1945 O 16 2 -5:30 - +0530 1996 May 25 -6:30 - +0630 1996 O 26 0:30 -6 - +06 2006 Ap 15 0:30 -5:30 - +0530 R S 1920 1923 - Ap Su>=15 2 1 S R S 1920 1923 - O Su>=1 2 0 - R S 1962 o - Ap 29 2 1 S @@ -1172,46 +768,6 @@ R S 2010 2011 - Ap F>=1 0 1 S R S 2012 2022 - Mar lastF 0 1 S R S 2009 2022 - O lastF 0 0 - -Z Asia/Damascus 2:25:12 - LMT 1920 -2 S EE%sT 2022 O 28 -3 - +03 -Z Asia/Dushanbe 4:35:12 - LMT 1924 May 2 -5 - +05 1930 Jun 21 -6 R +06/+07 1991 Mar 31 2s -5 1 +06 1991 S 9 2s -5 - +05 -Z Asia/Bangkok 6:42:4 - LMT 1880 -6:42:4 - BMT 1920 Ap -7 - +07 -Z Asia/Ashgabat 3:53:32 - LMT 1924 May 2 -4 - +04 1930 Jun 21 -5 R +05/+06 1991 Mar 31 2 -4 R +04/+05 1992 Ja 19 2 -5 - +05 -Z Asia/Dubai 3:41:12 - LMT 1920 -4 - +04 -Z Asia/Samarkand 4:27:53 - LMT 1924 May 2 -4 - +04 1930 Jun 21 -5 - +05 1981 Ap -5 1 +06 1981 O -6 - +06 1982 Ap -5 R +05/+06 1992 -5 - +05 -Z Asia/Tashkent 4:37:11 - LMT 1924 May 2 -5 - +05 1930 Jun 21 -6 R +06/+07 1991 Mar 31 2 -5 R +05/+06 1992 -5 - +05 -Z Asia/Ho_Chi_Minh 7:6:30 - LMT 1906 Jul -7:6:30 - PLMT 1911 May -7 - +07 1942 D 31 23 -8 - +08 1945 Mar 14 23 -9 - +09 1945 S 2 -7 - +07 1947 Ap -8 - +08 1955 Jul -7 - +07 1959 D 31 23 -8 - +08 1975 Jun 13 -7 - +07 R AU 1917 o - Ja 1 2s 1 D R AU 1917 o - Mar lastSu 2s 0 S R AU 1942 o - Ja 1 2s 1 D @@ -1219,9 +775,6 @@ R AU 1942 o - S 27 2s 1 D R AU 1943 1944 - Mar lastSu 2s 0 S R AU 1943 o - O 3 2s 1 D -Z Australia/Darwin 8:43:20 - LMT 1895 F -9 - ACST 1899 May -9:30 AU AC%sT R AW 1974 o - O lastSu 2s 1 D R AW 1975 o - Mar Su>=1 2s 0 S R AW 1983 o - O lastSu 2s 1 D @@ -1231,25 +784,12 @@ R AW 2006 o - D 3 2s 1 D R AW 2007 2009 - Mar lastSu 2s 0 S R AW 2007 2008 - O lastSu 2s 1 D -Z Australia/Perth 7:43:24 - LMT 1895 D -8 AU AW%sT 1943 Jul -8 AW AW%sT -Z Australia/Eucla 8:35:28 - LMT 1895 D -8:45 AU +0845/+0945 1943 Jul -8:45 AW +0845/+0945 R AQ 1971 o - O lastSu 2s 1 D R AQ 1972 o - F lastSu 2s 0 S R AQ 1989 1991 - O lastSu 2s 1 D R AQ 1990 1992 - Mar Su>=1 2s 0 S R Ho 1992 1993 - O lastSu 2s 1 D R Ho 1993 1994 - Mar Su>=1 2s 0 S -Z Australia/Brisbane 10:12:8 - LMT 1895 -10 AU AE%sT 1971 -10 AQ AE%sT -Z Australia/Lindeman 9:55:56 - LMT 1895 -10 AU AE%sT 1971 -10 AQ AE%sT 1992 Jul -10 Ho AE%sT R AS 1971 1985 - O lastSu 2s 1 D R AS 1986 o - O 19 2s 1 D R AS 1987 2007 - O lastSu 2s 1 D @@ -1265,10 +805,6 @@ R AS 2007 o - Mar lastSu 2s 0 S R AS 2008 ma - Ap Su>=1 2s 0 S R AS 2008 ma - O Su>=1 2s 1 D -Z Australia/Adelaide 9:14:20 - LMT 1895 F -9 - ACST 1899 May -9:30 AU AC%sT 1971 -9:30 AS AC%sT R AT 1916 o - O Su>=1 2s 1 D R AT 1917 o - Mar lastSu 2s 0 S R AT 1917 1918 - O Su>=22 2s 1 D @@ -1292,10 +828,6 @@ R AT 2006 o - Ap Su>=1 2s 0 S R AT 2007 o - Mar lastSu 2s 0 S R AT 2008 ma - Ap Su>=1 2s 0 S -Z Australia/Hobart 9:49:16 - LMT 1895 S -10 AT AE%sT 1919 O 24 -10 AU AE%sT 1967 -10 AT AE%sT R AV 1971 1985 - O lastSu 2s 1 D R AV 1972 o - F lastSu 2s 0 S R AV 1973 1985 - Mar Su>=1 2s 0 S @@ -1310,9 +842,6 @@ R AV 2007 o - Mar lastSu 2s 0 S R AV 2008 ma - Ap Su>=1 2s 0 S R AV 2008 ma - O Su>=1 2s 1 D -Z Australia/Melbourne 9:39:52 - LMT 1895 F -10 AU AE%sT 1971 -10 AV AE%sT R AN 1971 1985 - O lastSu 2s 1 D R AN 1972 o - F 27 2s 0 S R AN 1973 1981 - Mar Su>=1 2s 0 S @@ -1329,15 +858,6 @@ R AN 2007 o - Mar lastSu 2s 0 S R AN 2008 ma - Ap Su>=1 2s 0 S R AN 2008 ma - O Su>=1 2s 1 D -Z Australia/Sydney 10:4:52 - LMT 1895 F -10 AU AE%sT 1971 -10 AN AE%sT -Z Australia/Broken_Hill 9:25:48 - LMT 1895 F -10 - AEST 1896 Au 23 -9 - ACST 1899 May -9:30 AU AC%sT 1971 -9:30 AN AC%sT 2000 -9:30 AS AC%sT R LH 1981 1984 - O lastSu 2 1 - R LH 1982 1985 - Mar Su>=1 2 0 - R LH 1985 o - O lastSu 2 0:30 - @@ -1352,19 +872,6 @@ R LH 2007 o - Mar lastSu 2 0 - R LH 2008 ma - Ap Su>=1 2 0 - R LH 2008 ma - O Su>=1 2 0:30 - -Z Australia/Lord_Howe 10:36:20 - LMT 1895 F -10 - AEST 1981 Mar -10:30 LH +1030/+1130 1985 Jul -10:30 LH +1030/+11 -Z Antarctica/Macquarie 0 - -00 1899 N -10 - AEST 1916 O 1 2 -10 1 AEDT 1917 F -10 AU AE%sT 1919 Ap 1 0s -0 - -00 1948 Mar 25 -10 AU AE%sT 1967 -10 AT AE%sT 2010 -10 1 AEDT 2011 -10 AT AE%sT R FJ 1998 1999 - N Su>=1 2 1 - R FJ 1999 2000 - F lastSu 3 0 - R FJ 2009 o - N 29 2 1 - @@ -1377,14 +884,6 @@ R FJ 2015 2021 - Ja Su>=12 3 0 - R FJ 2019 o - N Su>=8 2 1 - R FJ 2020 o - D 20 2 1 - -Z Pacific/Fiji 11:55:44 - LMT 1915 O 26 -12 FJ +12/+13 -Z Pacific/Gambier -8:59:48 - LMT 1912 O --9 - -09 -Z Pacific/Marquesas -9:18 - LMT 1912 O --9:30 - -0930 -Z Pacific/Tahiti -9:58:16 - LMT 1912 O --10 - -10 R Gu 1959 o - Jun 27 2 1 D R Gu 1961 o - Ja 29 2 0 S R Gu 1967 o - S 1 2 1 D @@ -1399,50 +898,10 @@ R Gu 1976 o - Au 22 2:1 0 S R Gu 1977 o - Ap 24 2 1 D R Gu 1977 o - Au 28 2 0 S -Z Pacific/Guam -14:21 - LMT 1844 D 31 -9:39 - LMT 1901 -10 - GST 1941 D 10 -9 - +09 1944 Jul 31 -10 Gu G%sT 2000 D 23 -10 - ChST -Z Pacific/Tarawa 11:32:4 - LMT 1901 -12 - +12 -Z Pacific/Kanton 0 - -00 1937 Au 31 --12 - -12 1979 O --11 - -11 1994 D 31 -13 - +13 -Z Pacific/Kiritimati -10:29:20 - LMT 1901 --10:40 - -1040 1979 O --10 - -10 1994 D 31 -14 - +14 -Z Pacific/Kwajalein 11:9:20 - LMT 1901 -11 - +11 1937 -10 - +10 1941 Ap -9 - +09 1944 F 6 -11 - +11 1969 O --12 - -12 1993 Au 20 24 -12 - +12 -Z Pacific/Kosrae -13:8:4 - LMT 1844 D 31 -10:51:56 - LMT 1901 -11 - +11 1914 O -9 - +09 1919 F -11 - +11 1937 -10 - +10 1941 Ap -9 - +09 1945 Au -11 - +11 1969 O -12 - +12 1999 -11 - +11 -Z Pacific/Nauru 11:7:40 - LMT 1921 Ja 15 -11:30 - +1130 1942 Au 29 -9 - +09 1945 S 8 -11:30 - +1130 1979 F 10 2 -12 - +12 R NC 1977 1978 - D Su>=1 0 1 - R NC 1978 1979 - F 27 0 0 - R NC 1996 o - D 1 2s 1 - R NC 1997 o - Mar 2 2s 0 - -Z Pacific/Noumea 11:5:48 - LMT 1912 Ja 13 -11 NC +11/+12 R NZ 1927 o - N 6 2 1 S R NZ 1928 o - Mar 4 2 0 M R NZ 1928 1933 - O Su>=8 2 0:30 S @@ -1468,80 +927,26 @@ R k 2007 ma - S lastSu 2:45s 1 - R NZ 2008 ma - Ap Su>=1 2s 0 S R k 2008 ma - Ap Su>=1 2:45s 0 - -Z Pacific/Auckland 11:39:4 - LMT 1868 N 2 -11:30 NZ NZ%sT 1946 -12 NZ NZ%sT -Z Pacific/Chatham 12:13:48 - LMT 1868 N 2 -12:15 - +1215 1946 -12:45 k +1245/+1345 R CK 1978 o - N 12 0 0:30 - R CK 1979 1991 - Mar Su>=1 0 0 - R CK 1979 1990 - O lastSu 0 0:30 - -Z Pacific/Rarotonga 13:20:56 - LMT 1899 D 26 --10:39:4 - LMT 1952 O 16 --10:30 - -1030 1978 N 12 --10 CK -10/-0930 -Z Pacific/Niue -11:19:40 - LMT 1952 O 16 --11:20 - -1120 1964 Jul --11 - -11 -Z Pacific/Norfolk 11:11:52 - LMT 1901 -11:12 - +1112 1951 -11:30 - +1130 1974 O 27 2s -11:30 1 +1230 1975 Mar 2 2s -11:30 - +1130 2015 O 4 2s -11 - +11 2019 Jul -11 AN +11/+12 -Z Pacific/Palau -15:2:4 - LMT 1844 D 31 -8:57:56 - LMT 1901 -9 - +09 -Z Pacific/Port_Moresby 9:48:40 - LMT 1880 -9:48:32 - PMMT 1895 -10 - +10 -Z Pacific/Bougainville 10:22:16 - LMT 1880 -9:48:32 - PMMT 1895 -10 - +10 1942 Jul -9 - +09 1945 Au 21 -10 - +10 2014 D 28 2 -11 - +11 -Z Pacific/Pitcairn -8:40:20 - LMT 1901 --8:30 - -0830 1998 Ap 27 --8 - -08 -Z Pacific/Pago_Pago 12:37:12 - LMT 1892 Jul 5 --11:22:48 - LMT 1911 --11 - SST R WS 2010 o - S lastSu 0 1 - R WS 2011 o - Ap Sa>=1 4 0 - R WS 2011 o - S lastSa 3 1 - R WS 2012 2021 - Ap Su>=1 4 0 - R WS 2012 2020 - S lastSu 3 1 - -Z Pacific/Apia 12:33:4 - LMT 1892 Jul 5 --11:26:56 - LMT 1911 --11:30 - -1130 1950 --11 WS -11/-10 2011 D 29 24 -13 WS +13/+14 -Z Pacific/Guadalcanal 10:39:48 - LMT 1912 O -11 - +11 -Z Pacific/Fakaofo -11:24:56 - LMT 1901 --11 - -11 2011 D 30 -13 - +13 R TO 1999 o - O 7 2s 1 - R TO 2000 o - Mar 19 2s 0 - R TO 2000 2001 - N Su>=1 2 1 - R TO 2001 2002 - Ja lastSu 2 0 - R TO 2016 o - N Su>=1 2 1 - R TO 2017 o - Ja Su>=15 3 0 - -Z Pacific/Tongatapu 12:19:12 - LMT 1945 S 10 -12:20 - +1220 1961 -13 - +13 1999 -13 TO +13/+14 R VU 1973 o - D 22 12u 1 - R VU 1974 o - Mar 30 12u 0 - R VU 1983 1991 - S Sa>=22 24 1 - R VU 1984 1991 - Mar Sa>=22 24 0 - R VU 1992 1993 - Ja Sa>=22 24 0 - R VU 1992 o - O Sa>=22 24 1 - -Z Pacific/Efate 11:13:16 - LMT 1912 Ja 13 -11 VU +11/+12 R G 1916 o - May 21 2s 1 BST R G 1916 o - O 1 2s 0 GMT R G 1917 o - Ap 8 2s 1 BST @@ -1607,11 +1012,6 @@ R G 1981 1995 - Mar lastSu 1u 1 BST R G 1981 1989 - O Su>=23 1u 0 GMT R G 1990 1995 - O Su>=22 1u 0 GMT -Z Europe/London -0:1:15 - LMT 1847 D -0 G %s 1968 O 27 -1 - BST 1971 O 31 2u -0 G %s 1996 -0 E GMT/BST R IE 1971 o - O 31 2u -1 - R IE 1972 1980 - Mar Su>=16 2u 0 - R IE 1972 1980 - O Su>=23 2u -1 - @@ -1619,17 +1019,6 @@ R IE 1981 1989 - O Su>=23 1u -1 - R IE 1990 1995 - O Su>=22 1u -1 - R IE 1996 ma - O lastSu 1u -1 - -Z Europe/Dublin -0:25:21 - LMT 1880 Au 2 --0:25:21 - DMT 1916 May 21 2s --0:25:21 1 IST 1916 O 1 2s -0 G %s 1921 D 6 -0 G GMT/IST 1940 F 25 2s -0 1 IST 1946 O 6 2s -0 - GMT 1947 Mar 16 2s -0 1 IST 1947 N 2 2s -0 - GMT 1948 Ap 18 2s -0 G GMT/IST 1968 O 27 -1 IE IST/GMT R E 1977 1980 - Ap Su>=1 1u 1 S R E 1977 o - S lastSu 1u 0 - R E 1978 o - O 1 1u 0 - @@ -1681,10 +1070,6 @@ R R 1984 1995 - S lastSu 2s 0 - R R 1985 2010 - Mar lastSu 2s 1 S R R 1996 2010 - O lastSu 2s 0 - -Z WET 0 E WE%sT -Z CET 1 c CE%sT -Z MET 1 c ME%sT -Z EET 2 E EE%sT R q 1940 o - Jun 16 0 1 S R q 1942 o - N 2 3 0 - R q 1943 o - Mar 29 2 1 S @@ -1710,14 +1095,6 @@ R q 1983 o - Ap 18 0 1 S R q 1983 o - O 1 0 0 - R q 1984 o - Ap 1 0 1 S -Z Europe/Tirane 1:19:20 - LMT 1914 -1 - CET 1940 Jun 16 -1 q CE%sT 1984 Jul -1 E CE%sT -Z Europe/Andorra 0:6:4 - LMT 1901 -0 - WET 1946 S 30 -1 - CET 1985 Mar 31 2 -1 E CE%sT R a 1920 o - Ap 5 2s 1 S R a 1920 o - S 13 2s 0 - R a 1946 o - Ap 14 2s 1 S @@ -1727,23 +1104,6 @@ R a 1948 o - Ap 18 2s 1 S R a 1980 o - Ap 6 0 1 S R a 1980 o - S 28 0 0 - -Z Europe/Vienna 1:5:21 - LMT 1893 Ap -1 c CE%sT 1920 -1 a CE%sT 1940 Ap 1 2s -1 c CE%sT 1945 Ap 2 2s -1 1 CEST 1945 Ap 12 2s -1 - CET 1946 -1 a CE%sT 1981 -1 E CE%sT -Z Europe/Minsk 1:50:16 - LMT 1880 -1:50 - MMT 1924 May 2 -2 - EET 1930 Jun 21 -3 - MSK 1941 Jun 28 -1 c CE%sT 1944 Jul 3 -3 R MSK/MSD 1990 -3 - MSK 1991 Mar 31 2s -2 R EE%sT 2011 Mar 27 2s -3 - +03 R b 1918 o - Mar 9 0s 1 S R b 1918 1919 - O Sa>=1 23s 0 - R b 1919 o - Mar 1 23s 1 S @@ -1778,87 +1138,27 @@ R b 1945 o - S 16 2s 0 - R b 1946 o - May 19 2s 1 S R b 1946 o - O 7 2s 0 - -Z Europe/Brussels 0:17:30 - LMT 1880 -0:17:30 - BMT 1892 May 1 0:17:30 -0 - WET 1914 N 8 -1 - CET 1916 May -1 c CE%sT 1918 N 11 11u -0 b WE%sT 1940 May 20 2s -1 c CE%sT 1944 S 3 -1 b CE%sT 1977 -1 E CE%sT R BG 1979 o - Mar 31 23 1 S R BG 1979 o - O 1 1 0 - R BG 1980 1982 - Ap Sa>=1 23 1 S R BG 1980 o - S 29 1 0 - R BG 1981 o - S 27 2 0 - -Z Europe/Sofia 1:33:16 - LMT 1880 -1:56:56 - IMT 1894 N 30 -2 - EET 1942 N 2 3 -1 c CE%sT 1945 -1 - CET 1945 Ap 2 3 -2 - EET 1979 Mar 31 23 -2 BG EE%sT 1982 S 26 3 -2 c EE%sT 1991 -2 e EE%sT 1997 -2 E EE%sT R CZ 1945 o - Ap M>=1 2s 1 S R CZ 1945 o - O 1 2s 0 - R CZ 1946 o - May 6 2s 1 S R CZ 1946 1949 - O Su>=1 2s 0 - R CZ 1947 1948 - Ap Su>=15 2s 1 S R CZ 1949 o - Ap 9 2s 1 S -Z Europe/Prague 0:57:44 - LMT 1850 -0:57:44 - PMT 1891 O -1 c CE%sT 1945 May 9 -1 CZ CE%sT 1946 D 1 3 -1 -1 GMT 1947 F 23 2 -1 CZ CE%sT 1979 -1 E CE%sT -Z Atlantic/Faroe -0:27:4 - LMT 1908 Ja 11 -0 - WET 1981 -0 E WE%sT R Th 1991 1992 - Mar lastSu 2 1 D R Th 1991 1992 - S lastSu 2 0 S R Th 1993 2006 - Ap Su>=1 2 1 D R Th 1993 2006 - O lastSu 2 0 S R Th 2007 ma - Mar Su>=8 2 1 D R Th 2007 ma - N Su>=1 2 0 S -Z America/Danmarkshavn -1:14:40 - LMT 1916 Jul 28 --3 - -03 1980 Ap 6 2 --3 E -03/-02 1996 -0 - GMT -Z America/Scoresbysund -1:27:52 - LMT 1916 Jul 28 --2 - -02 1980 Ap 6 2 --2 c -02/-01 1981 Mar 29 --1 E -01/+00 -Z America/Nuuk -3:26:56 - LMT 1916 Jul 28 --3 - -03 1980 Ap 6 2 --3 E -03/-02 2023 O 29 1u --2 E -02/-01 -Z America/Thule -4:35:8 - LMT 1916 Jul 28 --4 Th A%sT -Z Europe/Tallinn 1:39 - LMT 1880 -1:39 - TMT 1918 F -1 c CE%sT 1919 Jul -1:39 - TMT 1921 May -2 - EET 1940 Au 6 -3 - MSK 1941 S 15 -1 c CE%sT 1944 S 22 -3 R MSK/MSD 1989 Mar 26 2s -2 1 EEST 1989 S 24 2s -2 c EE%sT 1998 S 22 -2 E EE%sT 1999 O 31 4 -2 - EET 2002 F 21 -2 E EE%sT R FI 1942 o - Ap 2 24 1 S R FI 1942 o - O 4 1 0 - R FI 1981 1982 - Mar lastSu 2 1 S R FI 1981 1982 - S lastSu 3 0 - -Z Europe/Helsinki 1:39:49 - LMT 1878 May 31 -1:39:49 - HMT 1921 May -2 FI EE%sT 1983 -2 E EE%sT R F 1916 o - Jun 14 23s 1 S R F 1916 1919 - O Su>=1 23s 0 - R F 1917 o - Mar 24 23s 1 S @@ -1901,13 +1201,6 @@ R F 1945 o - S 16 3 0 - R F 1976 o - Mar 28 1 1 S R F 1976 o - S 26 1 0 - -Z Europe/Paris 0:9:21 - LMT 1891 Mar 16 -0:9:21 - PMT 1911 Mar 11 -0 F WE%sT 1940 Jun 14 23 -1 c CE%sT 1944 Au 25 -0 F WE%sT 1945 S 16 3 -1 F CE%sT 1977 -1 E CE%sT R DE 1946 o - Ap 14 2s 1 S R DE 1946 o - O 7 2s 0 - R DE 1947 1949 - O Su>=1 2s 0 - @@ -1919,15 +1212,6 @@ R So 1945 o - May 24 2 2 M R So 1945 o - S 24 3 1 S R So 1945 o - N 18 2s 0 - -Z Europe/Berlin 0:53:28 - LMT 1893 Ap -1 c CE%sT 1945 May 24 2 -1 So CE%sT 1946 -1 DE CE%sT 1980 -1 E CE%sT -Z Europe/Gibraltar -0:21:24 - LMT 1880 Au 2 -0 G %s 1957 Ap 14 2 -1 - CET 1982 -1 E CE%sT R g 1932 o - Jul 7 0 1 S R g 1932 o - S 1 0 0 - R g 1941 o - Ap 7 0 1 S @@ -1947,12 +1231,6 @@ R g 1979 o - S 29 2 0 - R g 1980 o - Ap 1 0 1 S R g 1980 o - S 28 0 0 - -Z Europe/Athens 1:34:52 - LMT 1895 S 14 -1:34:52 - AMT 1916 Jul 28 0:1 -2 g EE%sT 1941 Ap 30 -1 g CE%sT 1944 Ap 4 -2 g EE%sT 1981 -2 E EE%sT R h 1918 1919 - Ap 15 2 1 S R h 1918 1920 - S M>=15 3 0 - R h 1920 o - Ap 5 2 1 S @@ -1972,12 +1250,6 @@ R h 1980 o - S 28 1 0 - R h 1981 1983 - Mar lastSu 0 1 S R h 1981 1983 - S lastSu 1 0 - -Z Europe/Budapest 1:16:20 - LMT 1890 N -1 c CE%sT 1918 -1 h CE%sT 1941 Ap 7 23 -1 c CE%sT 1945 -1 h CE%sT 1984 -1 E CE%sT R I 1916 o - Jun 3 24 1 S R I 1916 1917 - S 30 24 0 - R I 1917 o - Mar 31 24 1 S @@ -2019,44 +1291,8 @@ R I 1977 1979 - May Su>=22 0s 1 S R I 1978 o - O 1 0s 0 - R I 1979 o - S 30 0s 0 - -Z Europe/Rome 0:49:56 - LMT 1866 D 12 -0:49:56 - RMT 1893 O 31 23u -1 I CE%sT 1943 S 10 -1 c CE%sT 1944 Jun 4 -1 I CE%sT 1980 -1 E CE%sT R LV 1989 1996 - Mar lastSu 2s 1 S R LV 1989 1996 - S lastSu 2s 0 - -Z Europe/Riga 1:36:34 - LMT 1880 -1:36:34 - RMT 1918 Ap 15 2 -1:36:34 1 LST 1918 S 16 3 -1:36:34 - RMT 1919 Ap 1 2 -1:36:34 1 LST 1919 May 22 3 -1:36:34 - RMT 1926 May 11 -2 - EET 1940 Au 5 -3 - MSK 1941 Jul -1 c CE%sT 1944 O 13 -3 R MSK/MSD 1989 Mar lastSu 2s -2 1 EEST 1989 S lastSu 2s -2 LV EE%sT 1997 Ja 21 -2 E EE%sT 2000 F 29 -2 - EET 2001 Ja 2 -2 E EE%sT -Z Europe/Vilnius 1:41:16 - LMT 1880 -1:24 - WMT 1917 -1:35:36 - KMT 1919 O 10 -1 - CET 1920 Jul 12 -2 - EET 1920 O 9 -1 - CET 1940 Au 3 -3 - MSK 1941 Jun 24 -1 c CE%sT 1944 Au -3 R MSK/MSD 1989 Mar 26 2s -2 R EE%sT 1991 S 29 2s -2 c EE%sT 1998 -2 - EET 1998 Mar 29 1u -1 E CE%sT 1999 O 31 1u -2 - EET 2003 -2 E EE%sT R MT 1973 o - Mar 31 0s 1 S R MT 1973 o - S 29 0s 0 - R MT 1974 o - Ap 21 0s 1 S @@ -2064,22 +1300,8 @@ R MT 1975 1979 - Ap Su>=15 2 1 S R MT 1975 1980 - S Su>=15 2 0 - R MT 1980 o - Mar 31 2 1 S -Z Europe/Malta 0:58:4 - LMT 1893 N 2 -1 I CE%sT 1973 Mar 31 -1 MT CE%sT 1981 -1 E CE%sT R MD 1997 ma - Mar lastSu 2 1 S R MD 1997 ma - O lastSu 3 0 - -Z Europe/Chisinau 1:55:20 - LMT 1880 -1:55 - CMT 1918 F 15 -1:44:24 - BMT 1931 Jul 24 -2 z EE%sT 1940 Au 15 -2 1 EEST 1941 Jul 17 -1 c CE%sT 1944 Au 24 -3 R MSK/MSD 1990 May 6 2 -2 R EE%sT 1992 -2 e EE%sT 1997 -2 MD EE%sT R O 1918 1919 - S 16 2s 0 - R O 1919 o - Ap 15 2s 1 S R O 1944 o - Ap 3 2s 1 S @@ -2100,15 +1322,6 @@ R O 1960 o - Ap 3 1s 1 S R O 1961 1964 - May lastSu 1s 1 S R O 1962 1964 - S lastSu 1s 0 - -Z Europe/Warsaw 1:24 - LMT 1880 -1:24 - WMT 1915 Au 5 -1 c CE%sT 1918 S 16 3 -2 O EE%sT 1922 Jun -1 O CE%sT 1940 Jun 23 2 -1 c CE%sT 1944 O -1 O CE%sT 1977 -1 W- CE%sT 1988 -1 E CE%sT R p 1916 o - Jun 17 23 1 S R p 1916 o - N 1 1 0 - R p 1917 o - F 28 23s 1 S @@ -2157,42 +1370,6 @@ R p 1980 o - Mar lastSu 0s 1 S R p 1981 1982 - Mar lastSu 1s 1 S R p 1983 o - Mar lastSu 2s 1 S -Z Europe/Lisbon -0:36:45 - LMT 1884 --0:36:45 - LMT 1912 Ja 1 0u -0 p WE%sT 1966 Ap 3 2 -1 - CET 1976 S 26 1 -0 p WE%sT 1983 S 25 1s -0 W- WE%sT 1992 S 27 1s -1 E CE%sT 1996 Mar 31 1u -0 E WE%sT -Z Atlantic/Azores -1:42:40 - LMT 1884 --1:54:32 - HMT 1912 Ja 1 2u --2 p -02/-01 1942 Ap 25 22s --2 p +00 1942 Au 15 22s --2 p -02/-01 1943 Ap 17 22s --2 p +00 1943 Au 28 22s --2 p -02/-01 1944 Ap 22 22s --2 p +00 1944 Au 26 22s --2 p -02/-01 1945 Ap 21 22s --2 p +00 1945 Au 25 22s --2 p -02/-01 1966 Ap 3 2 --1 p -01/+00 1983 S 25 1s --1 W- -01/+00 1992 S 27 1s -0 E WE%sT 1993 Mar 28 1u --1 E -01/+00 -Z Atlantic/Madeira -1:7:36 - LMT 1884 --1:7:36 - FMT 1912 Ja 1 1u --1 p -01/+00 1942 Ap 25 22s --1 p +01 1942 Au 15 22s --1 p -01/+00 1943 Ap 17 22s --1 p +01 1943 Au 28 22s --1 p -01/+00 1944 Ap 22 22s --1 p +01 1944 Au 26 22s --1 p -01/+00 1945 Ap 21 22s --1 p +01 1945 Au 25 22s --1 p -01/+00 1966 Ap 3 2 -0 p WE%sT 1983 S 25 1s -0 E WE%sT R z 1932 o - May 21 0s 1 S R z 1932 1939 - O Su>=1 0s 0 - R z 1933 1939 - Ap Su>=2 0s 1 S @@ -2202,252 +1379,6 @@ R z 1980 o - S lastSu 1 0 - R z 1991 1993 - Mar lastSu 0s 1 S R z 1991 1993 - S lastSu 0s 0 - -Z Europe/Bucharest 1:44:24 - LMT 1891 O -1:44:24 - BMT 1931 Jul 24 -2 z EE%sT 1981 Mar 29 2s -2 c EE%sT 1991 -2 z EE%sT 1994 -2 e EE%sT 1997 -2 E EE%sT -Z Europe/Kaliningrad 1:22 - LMT 1893 Ap -1 c CE%sT 1945 Ap 10 -2 O EE%sT 1946 Ap 7 -3 R MSK/MSD 1989 Mar 26 2s -2 R EE%sT 2011 Mar 27 2s -3 - +03 2014 O 26 2s -2 - EET -Z Europe/Moscow 2:30:17 - LMT 1880 -2:30:17 - MMT 1916 Jul 3 -2:31:19 R %s 1919 Jul 1 0u -3 R %s 1921 O -3 R MSK/MSD 1922 O -2 - EET 1930 Jun 21 -3 R MSK/MSD 1991 Mar 31 2s -2 R EE%sT 1992 Ja 19 2s -3 R MSK/MSD 2011 Mar 27 2s -4 - MSK 2014 O 26 2s -3 - MSK -Z Europe/Simferopol 2:16:24 - LMT 1880 -2:16 - SMT 1924 May 2 -2 - EET 1930 Jun 21 -3 - MSK 1941 N -1 c CE%sT 1944 Ap 13 -3 R MSK/MSD 1990 -3 - MSK 1990 Jul 1 2 -2 - EET 1992 Mar 20 -2 c EE%sT 1994 May -3 c MSK/MSD 1996 Mar 31 0s -3 1 MSD 1996 O 27 3s -3 - MSK 1997 Mar lastSu 1u -2 E EE%sT 2014 Mar 30 2 -4 - MSK 2014 O 26 2s -3 - MSK -Z Europe/Astrakhan 3:12:12 - LMT 1924 May -3 - +03 1930 Jun 21 -4 R +04/+05 1989 Mar 26 2s -3 R +03/+04 1991 Mar 31 2s -4 - +04 1992 Mar 29 2s -3 R +03/+04 2011 Mar 27 2s -4 - +04 2014 O 26 2s -3 - +03 2016 Mar 27 2s -4 - +04 -Z Europe/Volgograd 2:57:40 - LMT 1920 Ja 3 -3 - +03 1930 Jun 21 -4 - +04 1961 N 11 -4 R +04/+05 1988 Mar 27 2s -3 R MSK/MSD 1991 Mar 31 2s -4 - +04 1992 Mar 29 2s -3 R MSK/MSD 2011 Mar 27 2s -4 - MSK 2014 O 26 2s -3 - MSK 2018 O 28 2s -4 - +04 2020 D 27 2s -3 - MSK -Z Europe/Saratov 3:4:18 - LMT 1919 Jul 1 0u -3 - +03 1930 Jun 21 -4 R +04/+05 1988 Mar 27 2s -3 R +03/+04 1991 Mar 31 2s -4 - +04 1992 Mar 29 2s -3 R +03/+04 2011 Mar 27 2s -4 - +04 2014 O 26 2s -3 - +03 2016 D 4 2s -4 - +04 -Z Europe/Kirov 3:18:48 - LMT 1919 Jul 1 0u -3 - +03 1930 Jun 21 -4 R +04/+05 1989 Mar 26 2s -3 R MSK/MSD 1991 Mar 31 2s -4 - +04 1992 Mar 29 2s -3 R MSK/MSD 2011 Mar 27 2s -4 - MSK 2014 O 26 2s -3 - MSK -Z Europe/Samara 3:20:20 - LMT 1919 Jul 1 0u -3 - +03 1930 Jun 21 -4 - +04 1935 Ja 27 -4 R +04/+05 1989 Mar 26 2s -3 R +03/+04 1991 Mar 31 2s -2 R +02/+03 1991 S 29 2s -3 - +03 1991 O 20 3 -4 R +04/+05 2010 Mar 28 2s -3 R +03/+04 2011 Mar 27 2s -4 - +04 -Z Europe/Ulyanovsk 3:13:36 - LMT 1919 Jul 1 0u -3 - +03 1930 Jun 21 -4 R +04/+05 1989 Mar 26 2s -3 R +03/+04 1991 Mar 31 2s -2 R +02/+03 1992 Ja 19 2s -3 R +03/+04 2011 Mar 27 2s -4 - +04 2014 O 26 2s -3 - +03 2016 Mar 27 2s -4 - +04 -Z Asia/Yekaterinburg 4:2:33 - LMT 1916 Jul 3 -3:45:5 - PMT 1919 Jul 15 4 -4 - +04 1930 Jun 21 -5 R +05/+06 1991 Mar 31 2s -4 R +04/+05 1992 Ja 19 2s -5 R +05/+06 2011 Mar 27 2s -6 - +06 2014 O 26 2s -5 - +05 -Z Asia/Omsk 4:53:30 - LMT 1919 N 14 -5 - +05 1930 Jun 21 -6 R +06/+07 1991 Mar 31 2s -5 R +05/+06 1992 Ja 19 2s -6 R +06/+07 2011 Mar 27 2s -7 - +07 2014 O 26 2s -6 - +06 -Z Asia/Barnaul 5:35 - LMT 1919 D 10 -6 - +06 1930 Jun 21 -7 R +07/+08 1991 Mar 31 2s -6 R +06/+07 1992 Ja 19 2s -7 R +07/+08 1995 May 28 -6 R +06/+07 2011 Mar 27 2s -7 - +07 2014 O 26 2s -6 - +06 2016 Mar 27 2s -7 - +07 -Z Asia/Novosibirsk 5:31:40 - LMT 1919 D 14 6 -6 - +06 1930 Jun 21 -7 R +07/+08 1991 Mar 31 2s -6 R +06/+07 1992 Ja 19 2s -7 R +07/+08 1993 May 23 -6 R +06/+07 2011 Mar 27 2s -7 - +07 2014 O 26 2s -6 - +06 2016 Jul 24 2s -7 - +07 -Z Asia/Tomsk 5:39:51 - LMT 1919 D 22 -6 - +06 1930 Jun 21 -7 R +07/+08 1991 Mar 31 2s -6 R +06/+07 1992 Ja 19 2s -7 R +07/+08 2002 May 1 3 -6 R +06/+07 2011 Mar 27 2s -7 - +07 2014 O 26 2s -6 - +06 2016 May 29 2s -7 - +07 -Z Asia/Novokuznetsk 5:48:48 - LMT 1924 May -6 - +06 1930 Jun 21 -7 R +07/+08 1991 Mar 31 2s -6 R +06/+07 1992 Ja 19 2s -7 R +07/+08 2010 Mar 28 2s -6 R +06/+07 2011 Mar 27 2s -7 - +07 -Z Asia/Krasnoyarsk 6:11:26 - LMT 1920 Ja 6 -6 - +06 1930 Jun 21 -7 R +07/+08 1991 Mar 31 2s -6 R +06/+07 1992 Ja 19 2s -7 R +07/+08 2011 Mar 27 2s -8 - +08 2014 O 26 2s -7 - +07 -Z Asia/Irkutsk 6:57:5 - LMT 1880 -6:57:5 - IMT 1920 Ja 25 -7 - +07 1930 Jun 21 -8 R +08/+09 1991 Mar 31 2s -7 R +07/+08 1992 Ja 19 2s -8 R +08/+09 2011 Mar 27 2s -9 - +09 2014 O 26 2s -8 - +08 -Z Asia/Chita 7:33:52 - LMT 1919 D 15 -8 - +08 1930 Jun 21 -9 R +09/+10 1991 Mar 31 2s -8 R +08/+09 1992 Ja 19 2s -9 R +09/+10 2011 Mar 27 2s -10 - +10 2014 O 26 2s -8 - +08 2016 Mar 27 2 -9 - +09 -Z Asia/Yakutsk 8:38:58 - LMT 1919 D 15 -8 - +08 1930 Jun 21 -9 R +09/+10 1991 Mar 31 2s -8 R +08/+09 1992 Ja 19 2s -9 R +09/+10 2011 Mar 27 2s -10 - +10 2014 O 26 2s -9 - +09 -Z Asia/Vladivostok 8:47:31 - LMT 1922 N 15 -9 - +09 1930 Jun 21 -10 R +10/+11 1991 Mar 31 2s -9 R +09/+10 1992 Ja 19 2s -10 R +10/+11 2011 Mar 27 2s -11 - +11 2014 O 26 2s -10 - +10 -Z Asia/Khandyga 9:2:13 - LMT 1919 D 15 -8 - +08 1930 Jun 21 -9 R +09/+10 1991 Mar 31 2s -8 R +08/+09 1992 Ja 19 2s -9 R +09/+10 2004 -10 R +10/+11 2011 Mar 27 2s -11 - +11 2011 S 13 0s -10 - +10 2014 O 26 2s -9 - +09 -Z Asia/Sakhalin 9:30:48 - LMT 1905 Au 23 -9 - +09 1945 Au 25 -11 R +11/+12 1991 Mar 31 2s -10 R +10/+11 1992 Ja 19 2s -11 R +11/+12 1997 Mar lastSu 2s -10 R +10/+11 2011 Mar 27 2s -11 - +11 2014 O 26 2s -10 - +10 2016 Mar 27 2s -11 - +11 -Z Asia/Magadan 10:3:12 - LMT 1924 May 2 -10 - +10 1930 Jun 21 -11 R +11/+12 1991 Mar 31 2s -10 R +10/+11 1992 Ja 19 2s -11 R +11/+12 2011 Mar 27 2s -12 - +12 2014 O 26 2s -10 - +10 2016 Ap 24 2s -11 - +11 -Z Asia/Srednekolymsk 10:14:52 - LMT 1924 May 2 -10 - +10 1930 Jun 21 -11 R +11/+12 1991 Mar 31 2s -10 R +10/+11 1992 Ja 19 2s -11 R +11/+12 2011 Mar 27 2s -12 - +12 2014 O 26 2s -11 - +11 -Z Asia/Ust-Nera 9:32:54 - LMT 1919 D 15 -8 - +08 1930 Jun 21 -9 R +09/+10 1981 Ap -11 R +11/+12 1991 Mar 31 2s -10 R +10/+11 1992 Ja 19 2s -11 R +11/+12 2011 Mar 27 2s -12 - +12 2011 S 13 0s -11 - +11 2014 O 26 2s -10 - +10 -Z Asia/Kamchatka 10:34:36 - LMT 1922 N 10 -11 - +11 1930 Jun 21 -12 R +12/+13 1991 Mar 31 2s -11 R +11/+12 1992 Ja 19 2s -12 R +12/+13 2010 Mar 28 2s -11 R +11/+12 2011 Mar 27 2s -12 - +12 -Z Asia/Anadyr 11:49:56 - LMT 1924 May 2 -12 - +12 1930 Jun 21 -13 R +13/+14 1982 Ap 1 0s -12 R +12/+13 1991 Mar 31 2s -11 R +11/+12 1992 Ja 19 2s -12 R +12/+13 2010 Mar 28 2s -11 R +11/+12 2011 Mar 27 2s -12 - +12 -Z Europe/Belgrade 1:22 - LMT 1884 -1 - CET 1941 Ap 18 23 -1 c CE%sT 1945 -1 - CET 1945 May 8 2s -1 1 CEST 1945 S 16 2s -1 - CET 1982 N 27 -1 E CE%sT R s 1918 o - Ap 15 23 1 S R s 1918 1919 - O 6 24s 0 - R s 1919 o - Ap 6 23 1 S @@ -2487,30 +1418,8 @@ R Sp 1977 o - S 28 0 0 - R Sp 1978 o - Jun 1 0 1 S R Sp 1978 o - Au 4 0 0 - -Z Europe/Madrid -0:14:44 - LMT 1901 Ja 1 0u -0 s WE%sT 1940 Mar 16 23 -1 s CE%sT 1979 -1 E CE%sT -Z Africa/Ceuta -0:21:16 - LMT 1901 Ja 1 0u -0 - WET 1918 May 6 23 -0 1 WEST 1918 O 7 23 -0 - WET 1924 -0 s WE%sT 1929 -0 - WET 1967 -0 Sp WE%sT 1984 Mar 16 -1 - CET 1986 -1 E CE%sT -Z Atlantic/Canary -1:1:36 - LMT 1922 Mar --1 - -01 1946 S 30 1 -0 - WET 1980 Ap 6 0s -0 1 WEST 1980 S 28 1u -0 E WE%sT R CH 1941 1942 - May M>=1 1 1 S R CH 1941 1942 - O M>=1 2 0 - -Z Europe/Zurich 0:34:8 - LMT 1853 Jul 16 -0:29:46 - BMT 1894 Jun -1 CH CE%sT 1981 -1 E CE%sT R T 1916 o - May 1 0 1 S R T 1916 o - O 1 0 0 - R T 1920 o - Mar 28 0 1 S @@ -2556,28 +1465,6 @@ R T 1994 o - Mar 20 1s 1 S R T 1995 2006 - Mar lastSu 1s 1 S R T 1996 2006 - O lastSu 1s 0 - -Z Europe/Istanbul 1:55:52 - LMT 1880 -1:56:56 - IMT 1910 O -2 T EE%sT 1978 Jun 29 -3 T +03/+04 1984 N 1 2 -2 T EE%sT 2007 -2 E EE%sT 2011 Mar 27 1u -2 - EET 2011 Mar 28 1u -2 E EE%sT 2014 Mar 30 1u -2 - EET 2014 Mar 31 1u -2 E EE%sT 2015 O 25 1u -2 1 EEST 2015 N 8 1u -2 E EE%sT 2016 S 7 -3 - +03 -Z Europe/Kyiv 2:2:4 - LMT 1880 -2:2:4 - KMT 1924 May 2 -2 - EET 1930 Jun 21 -3 - MSK 1941 S 20 -1 c CE%sT 1943 N 6 -3 R MSK/MSD 1990 Jul 1 2 -2 1 EEST 1991 S 29 3 -2 c EE%sT 1996 May 13 -2 E EE%sT R u 1918 1919 - Mar lastSu 2 1 D R u 1918 1919 - O lastSu 2 0 S R u 1942 o - F 9 2 1 W @@ -2591,172 +1478,34 @@ R u 1987 2006 - Ap Su>=1 2 1 D R u 2007 ma - Mar Su>=8 2 1 D R u 2007 ma - N Su>=1 2 0 S -Z EST -5 - EST -Z MST -7 - MST -Z HST -10 - HST -Z EST5EDT -5 u E%sT -Z CST6CDT -6 u C%sT -Z MST7MDT -7 u M%sT -Z PST8PDT -8 u P%sT R NY 1920 o - Mar lastSu 2 1 D R NY 1920 o - O lastSu 2 0 S R NY 1921 1966 - Ap lastSu 2 1 D R NY 1921 1954 - S lastSu 2 0 S R NY 1955 1966 - O lastSu 2 0 S -Z America/New_York -4:56:2 - LMT 1883 N 18 17u --5 u E%sT 1920 --5 NY E%sT 1942 --5 u E%sT 1946 --5 NY E%sT 1967 --5 u E%sT R Ch 1920 o - Jun 13 2 1 D R Ch 1920 1921 - O lastSu 2 0 S R Ch 1921 o - Mar lastSu 2 1 D R Ch 1922 1966 - Ap lastSu 2 1 D R Ch 1922 1954 - S lastSu 2 0 S R Ch 1955 1966 - O lastSu 2 0 S -Z America/Chicago -5:50:36 - LMT 1883 N 18 18u --6 u C%sT 1920 --6 Ch C%sT 1936 Mar 1 2 --5 - EST 1936 N 15 2 --6 Ch C%sT 1942 --6 u C%sT 1946 --6 Ch C%sT 1967 --6 u C%sT -Z America/North_Dakota/Center -6:45:12 - LMT 1883 N 18 19u --7 u M%sT 1992 O 25 2 --6 u C%sT -Z America/North_Dakota/New_Salem -6:45:39 - LMT 1883 N 18 19u --7 u M%sT 2003 O 26 2 --6 u C%sT -Z America/North_Dakota/Beulah -6:47:7 - LMT 1883 N 18 19u --7 u M%sT 2010 N 7 2 --6 u C%sT R De 1920 1921 - Mar lastSu 2 1 D R De 1920 o - O lastSu 2 0 S R De 1921 o - May 22 2 0 S R De 1965 1966 - Ap lastSu 2 1 D R De 1965 1966 - O lastSu 2 0 S -Z America/Denver -6:59:56 - LMT 1883 N 18 19u --7 u M%sT 1920 --7 De M%sT 1942 --7 u M%sT 1946 --7 De M%sT 1967 --7 u M%sT R CA 1948 o - Mar 14 2:1 1 D R CA 1949 o - Ja 1 2 0 S R CA 1950 1966 - Ap lastSu 1 1 D R CA 1950 1961 - S lastSu 2 0 S R CA 1962 1966 - O lastSu 2 0 S -Z America/Los_Angeles -7:52:58 - LMT 1883 N 18 20u --8 u P%sT 1946 --8 CA P%sT 1967 --8 u P%sT -Z America/Juneau 15:2:19 - LMT 1867 O 19 15:33:32 --8:57:41 - LMT 1900 Au 20 12 --8 - PST 1942 --8 u P%sT 1946 --8 - PST 1969 --8 u P%sT 1980 Ap 27 2 --9 u Y%sT 1980 O 26 2 --8 u P%sT 1983 O 30 2 --9 u Y%sT 1983 N 30 --9 u AK%sT -Z America/Sitka 14:58:47 - LMT 1867 O 19 15:30 --9:1:13 - LMT 1900 Au 20 12 --8 - PST 1942 --8 u P%sT 1946 --8 - PST 1969 --8 u P%sT 1983 O 30 2 --9 u Y%sT 1983 N 30 --9 u AK%sT -Z America/Metlakatla 15:13:42 - LMT 1867 O 19 15:44:55 --8:46:18 - LMT 1900 Au 20 12 --8 - PST 1942 --8 u P%sT 1946 --8 - PST 1969 --8 u P%sT 1983 O 30 2 --8 - PST 2015 N 1 2 --9 u AK%sT 2018 N 4 2 --8 - PST 2019 Ja 20 2 --9 u AK%sT -Z America/Yakutat 14:41:5 - LMT 1867 O 19 15:12:18 --9:18:55 - LMT 1900 Au 20 12 --9 - YST 1942 --9 u Y%sT 1946 --9 - YST 1969 --9 u Y%sT 1983 N 30 --9 u AK%sT -Z America/Anchorage 14:0:24 - LMT 1867 O 19 14:31:37 --9:59:36 - LMT 1900 Au 20 12 --10 - AST 1942 --10 u A%sT 1967 Ap --10 - AHST 1969 --10 u AH%sT 1983 O 30 2 --9 u Y%sT 1983 N 30 --9 u AK%sT -Z America/Nome 12:58:22 - LMT 1867 O 19 13:29:35 --11:1:38 - LMT 1900 Au 20 12 --11 - NST 1942 --11 u N%sT 1946 --11 - NST 1967 Ap --11 - BST 1969 --11 u B%sT 1983 O 30 2 --9 u Y%sT 1983 N 30 --9 u AK%sT -Z America/Adak 12:13:22 - LMT 1867 O 19 12:44:35 --11:46:38 - LMT 1900 Au 20 12 --11 - NST 1942 --11 u N%sT 1946 --11 - NST 1967 Ap --11 - BST 1969 --11 u B%sT 1983 O 30 2 --10 u AH%sT 1983 N 30 --10 u H%sT -Z Pacific/Honolulu -10:31:26 - LMT 1896 Ja 13 12 --10:30 - HST 1933 Ap 30 2 --10:30 1 HDT 1933 May 21 12 --10:30 u H%sT 1947 Jun 8 2 --10 - HST -Z America/Phoenix -7:28:18 - LMT 1883 N 18 19u --7 u M%sT 1944 Ja 1 0:1 --7 - MST 1944 Ap 1 0:1 --7 u M%sT 1944 O 1 0:1 --7 - MST 1967 --7 u M%sT 1968 Mar 21 --7 - MST -Z America/Boise -7:44:49 - LMT 1883 N 18 20u --8 u P%sT 1923 May 13 2 --7 u M%sT 1974 --7 - MST 1974 F 3 2 --7 u M%sT R In 1941 o - Jun 22 2 1 D R In 1941 1954 - S lastSu 2 0 S R In 1946 1954 - Ap lastSu 2 1 D -Z America/Indiana/Indianapolis -5:44:38 - LMT 1883 N 18 18u --6 u C%sT 1920 --6 In C%sT 1942 --6 u C%sT 1946 --6 In C%sT 1955 Ap 24 2 --5 - EST 1957 S 29 2 --6 - CST 1958 Ap 27 2 --5 - EST 1969 --5 u E%sT 1971 --5 - EST 2006 --5 u E%sT R Ma 1951 o - Ap lastSu 2 1 D R Ma 1951 o - S lastSu 2 0 S R Ma 1954 1960 - Ap lastSu 2 1 D R Ma 1954 1960 - S lastSu 2 0 S -Z America/Indiana/Marengo -5:45:23 - LMT 1883 N 18 18u --6 u C%sT 1951 --6 Ma C%sT 1961 Ap 30 2 --5 - EST 1969 --5 u E%sT 1974 Ja 6 2 --6 1 CDT 1974 O 27 2 --5 u E%sT 1976 --5 - EST 2006 --5 u E%sT R V 1946 o - Ap lastSu 2 1 D R V 1946 o - S lastSu 2 0 S R V 1953 1954 - Ap lastSu 2 1 D @@ -2766,68 +1515,23 @@ R V 1960 o - O lastSu 2 0 S R V 1961 o - S lastSu 2 0 S R V 1962 1963 - O lastSu 2 0 S -Z America/Indiana/Vincennes -5:50:7 - LMT 1883 N 18 18u --6 u C%sT 1946 --6 V C%sT 1964 Ap 26 2 --5 - EST 1969 --5 u E%sT 1971 --5 - EST 2006 Ap 2 2 --6 u C%sT 2007 N 4 2 --5 u E%sT R Pe 1955 o - May 1 0 1 D R Pe 1955 1960 - S lastSu 2 0 S R Pe 1956 1963 - Ap lastSu 2 1 D R Pe 1961 1963 - O lastSu 2 0 S -Z America/Indiana/Tell_City -5:47:3 - LMT 1883 N 18 18u --6 u C%sT 1946 --6 Pe C%sT 1964 Ap 26 2 --5 - EST 1967 O 29 2 --6 u C%sT 1969 Ap 27 2 --5 u E%sT 1971 --5 - EST 2006 Ap 2 2 --6 u C%sT R Pi 1955 o - May 1 0 1 D R Pi 1955 1960 - S lastSu 2 0 S R Pi 1956 1964 - Ap lastSu 2 1 D R Pi 1961 1964 - O lastSu 2 0 S -Z America/Indiana/Petersburg -5:49:7 - LMT 1883 N 18 18u --6 u C%sT 1955 --6 Pi C%sT 1965 Ap 25 2 --5 - EST 1966 O 30 2 --6 u C%sT 1977 O 30 2 --5 - EST 2006 Ap 2 2 --6 u C%sT 2007 N 4 2 --5 u E%sT R St 1947 1961 - Ap lastSu 2 1 D R St 1947 1954 - S lastSu 2 0 S R St 1955 1956 - O lastSu 2 0 S R St 1957 1958 - S lastSu 2 0 S R St 1959 1961 - O lastSu 2 0 S -Z America/Indiana/Knox -5:46:30 - LMT 1883 N 18 18u --6 u C%sT 1947 --6 St C%sT 1962 Ap 29 2 --5 - EST 1963 O 27 2 --6 u C%sT 1991 O 27 2 --5 - EST 2006 Ap 2 2 --6 u C%sT R Pu 1946 1960 - Ap lastSu 2 1 D R Pu 1946 1954 - S lastSu 2 0 S R Pu 1955 1956 - O lastSu 2 0 S R Pu 1957 1960 - S lastSu 2 0 S -Z America/Indiana/Winamac -5:46:25 - LMT 1883 N 18 18u --6 u C%sT 1946 --6 Pu C%sT 1961 Ap 30 2 --5 - EST 1969 --5 u E%sT 1971 --5 - EST 2006 Ap 2 2 --6 u C%sT 2007 Mar 11 2 --5 u E%sT -Z America/Indiana/Vevay -5:40:16 - LMT 1883 N 18 18u --6 u C%sT 1954 Ap 25 2 --5 - EST 1969 --5 u E%sT 1973 --5 - EST 2006 --5 u E%sT R v 1921 o - May 1 2 1 D R v 1921 o - S 1 2 0 S R v 1941 o - Ap lastSu 2 1 D @@ -2837,41 +1541,12 @@ R v 1950 1961 - Ap lastSu 2 1 D R v 1950 1955 - S lastSu 2 0 S R v 1956 1961 - O lastSu 2 0 S -Z America/Kentucky/Louisville -5:43:2 - LMT 1883 N 18 18u --6 u C%sT 1921 --6 v C%sT 1942 --6 u C%sT 1946 --6 v C%sT 1961 Jul 23 2 --5 - EST 1968 --5 u E%sT 1974 Ja 6 2 --6 1 CDT 1974 O 27 2 --5 u E%sT -Z America/Kentucky/Monticello -5:39:24 - LMT 1883 N 18 18u --6 u C%sT 1946 --6 - CST 1968 --6 u C%sT 2000 O 29 2 --5 u E%sT R Dt 1948 o - Ap lastSu 2 1 D R Dt 1948 o - S lastSu 2 0 S -Z America/Detroit -5:32:11 - LMT 1905 --6 - CST 1915 May 15 2 --5 - EST 1942 --5 u E%sT 1946 --5 Dt E%sT 1967 Jun 14 0:1 --5 u E%sT 1969 --5 - EST 1973 --5 u E%sT 1975 --5 - EST 1975 Ap 27 2 --5 u E%sT R Me 1946 o - Ap lastSu 2 1 D R Me 1946 o - S lastSu 2 0 S R Me 1966 o - Ap lastSu 2 1 D R Me 1966 o - O lastSu 2 0 S -Z America/Menominee -5:50:27 - LMT 1885 S 18 12 --6 u C%sT 1946 --6 Me C%sT 1969 Ap 27 2 --5 - EST 1973 Ap 29 2 --6 u C%sT R C 1918 o - Ap 14 2 1 D R C 1918 o - O 27 2 0 S R C 1942 o - F 9 2 1 W @@ -2901,24 +1576,6 @@ R j 1989 2006 - Ap Su>=1 0:1 1 D R j 2007 2011 - Mar Su>=8 0:1 1 D R j 2007 2010 - N Su>=1 0:1 0 S -Z America/St_Johns -3:30:52 - LMT 1884 --3:30:52 j N%sT 1918 --3:30:52 C N%sT 1919 --3:30:52 j N%sT 1935 Mar 30 --3:30 j N%sT 1942 May 11 --3:30 C N%sT 1946 --3:30 j N%sT 2011 N --3:30 C N%sT -Z America/Goose_Bay -4:1:40 - LMT 1884 --3:30:52 - NST 1918 --3:30:52 C N%sT 1919 --3:30:52 - NST 1935 Mar 30 --3:30 - NST 1936 --3:30 j N%sT 1942 May 11 --3:30 C N%sT 1946 --3:30 j N%sT 1966 Mar 15 2 --4 j A%sT 2011 N --4 C A%sT R H 1916 o - Ap 1 0 1 D R H 1916 o - O 1 0 0 S R H 1920 o - May 9 0 1 D @@ -2960,19 +1617,6 @@ R H 1956 1959 - S lastSu 2 0 S R H 1962 1973 - Ap lastSu 2 1 D R H 1962 1973 - O lastSu 2 0 S -Z America/Halifax -4:14:24 - LMT 1902 Jun 15 --4 H A%sT 1918 --4 C A%sT 1919 --4 H A%sT 1942 F 9 2s --4 C A%sT 1946 --4 H A%sT 1974 --4 C A%sT -Z America/Glace_Bay -3:59:48 - LMT 1902 Jun 15 --4 C A%sT 1953 --4 H A%sT 1954 --4 - AST 1972 --4 H A%sT 1974 --4 C A%sT R o 1933 1935 - Jun Su>=8 1 1 D R o 1933 1935 - S Su>=8 1 0 S R o 1936 1938 - Jun Su>=1 1 1 D @@ -2986,15 +1630,6 @@ R o 1957 1972 - O lastSu 2 0 S R o 1993 2006 - Ap Su>=1 0:1 1 D R o 1993 2006 - O lastSu 0:1 0 S -Z America/Moncton -4:19:8 - LMT 1883 D 9 --5 - EST 1902 Jun 15 --4 C A%sT 1933 --4 o A%sT 1942 --4 C A%sT 1946 --4 o A%sT 1973 --4 C A%sT 1993 --4 o A%sT 2007 --4 C A%sT R t 1919 o - Mar 30 23:30 1 D R t 1919 o - O 26 0 0 S R t 1920 o - May 2 2 1 D @@ -3008,21 +1643,11 @@ R t 1928 1937 - Ap Su>=25 2 1 D R t 1938 1940 - Ap lastSu 2 1 D R t 1938 1939 - S lastSu 2 0 S -R t 1945 1946 - S lastSu 2 0 S -R t 1946 o - Ap lastSu 2 1 D -R t 1947 1949 - Ap lastSu 0 1 D -R t 1947 1948 - S lastSu 0 0 S -R t 1949 o - N lastSu 0 0 S -R t 1950 1973 - Ap lastSu 2 1 D -R t 1950 o - N lastSu 2 0 S +R t 1945 1948 - S lastSu 2 0 S +R t 1946 1973 - Ap lastSu 2 1 D +R t 1949 1950 - N lastSu 2 0 S R t 1951 1956 - S lastSu 2 0 S R t 1957 1973 - O lastSu 2 0 S -Z America/Toronto -5:17:32 - LMT 1895 --5 C E%sT 1919 --5 t E%sT 1942 F 9 2s --5 C E%sT 1946 --5 t E%sT 1974 --5 C E%sT R W 1916 o - Ap 23 0 1 D R W 1916 o - S 17 0 0 S R W 1918 o - Ap 14 2 1 D @@ -3047,9 +1672,6 @@ R W 1966 1986 - Ap lastSu 2s 1 D R W 1966 2005 - O lastSu 2s 0 S R W 1987 2005 - Ap Su>=1 2s 1 D -Z America/Winnipeg -6:28:36 - LMT 1887 Jul 16 --6 W C%sT 2006 --6 C C%sT R r 1918 o - Ap 14 2 1 D R r 1918 o - O 27 2 0 S R r 1930 1934 - May Su>=1 0 1 D @@ -3072,14 +1694,6 @@ R Sw 1959 1961 - Ap lastSu 2 1 D R Sw 1959 o - O lastSu 2 0 S R Sw 1960 1961 - S lastSu 2 0 S -Z America/Regina -6:58:36 - LMT 1905 S --7 r M%sT 1960 Ap lastSu 2 --6 - CST -Z America/Swift_Current -7:11:20 - LMT 1905 S --7 C M%sT 1946 Ap lastSu 2 --7 r M%sT 1950 --7 Sw M%sT 1972 Ap lastSu 2 --6 - CST R Ed 1918 1919 - Ap Su>=8 2 1 D R Ed 1918 o - O 27 2 0 S R Ed 1919 o - May 27 2 0 S @@ -3093,9 +1707,6 @@ R Ed 1947 o - S lastSu 2 0 S R Ed 1972 1986 - Ap lastSu 2 1 D R Ed 1972 2006 - O lastSu 2 0 S -Z America/Edmonton -7:33:52 - LMT 1906 S --7 Ed M%sT 1987 --7 C M%sT R Va 1918 o - Ap 14 2 1 D R Va 1918 o - O 27 2 0 S R Va 1942 o - F 9 2 1 W @@ -3105,19 +1716,6 @@ R Va 1946 o - S 29 2 0 S R Va 1947 1961 - S lastSu 2 0 S R Va 1962 2006 - O lastSu 2 0 S -Z America/Vancouver -8:12:28 - LMT 1884 --8 Va P%sT 1987 --8 C P%sT -Z America/Dawson_Creek -8:0:56 - LMT 1884 --8 C P%sT 1947 --8 Va P%sT 1972 Au 30 2 --7 - MST -Z America/Fort_Nelson -8:10:47 - LMT 1884 --8 Va P%sT 1946 --8 - PST 1947 --8 Va P%sT 1987 --8 C P%sT 2015 Mar 8 2 --7 - MST R Y 1918 o - Ap 14 2 1 D R Y 1918 o - O 27 2 0 S R Y 1919 o - May 25 2 1 D @@ -3130,42 +1728,6 @@ R Y 1987 2006 - Ap Su>=1 2 1 D R Yu 1965 o - Ap lastSu 0 2 DD R Yu 1965 o - O lastSu 2 0 S -Z America/Iqaluit 0 - -00 1942 Au --5 Y E%sT 1999 O 31 2 --6 C C%sT 2000 O 29 2 --5 C E%sT -Z America/Resolute 0 - -00 1947 Au 31 --6 Y C%sT 2000 O 29 2 --5 - EST 2001 Ap 1 3 --6 C C%sT 2006 O 29 2 --5 - EST 2007 Mar 11 3 --6 C C%sT -Z America/Rankin_Inlet 0 - -00 1957 --6 Y C%sT 2000 O 29 2 --5 - EST 2001 Ap 1 3 --6 C C%sT -Z America/Cambridge_Bay 0 - -00 1920 --7 Y M%sT 1999 O 31 2 --6 C C%sT 2000 O 29 2 --5 - EST 2000 N 5 --6 - CST 2001 Ap 1 3 --7 C M%sT -Z America/Inuvik 0 - -00 1953 --8 Y P%sT 1979 Ap lastSu 2 --7 Y M%sT 1980 --7 C M%sT -Z America/Whitehorse -9:0:12 - LMT 1900 Au 20 --9 Y Y%sT 1965 --9 Yu Y%sT 1966 F 27 --8 - PST 1980 --8 C P%sT 2020 N --7 - MST -Z America/Dawson -9:17:40 - LMT 1900 Au 20 --9 Y Y%sT 1965 --9 Yu Y%sT 1973 O 28 --8 - PST 1980 --8 C P%sT 2020 N --7 - MST R m 1931 o - May 1 23 1 D R m 1931 o - O 1 0 0 S R m 1939 o - F 5 0 1 D @@ -3182,107 +1744,6 @@ R m 2001 o - S lastSu 2 0 S R m 2002 2022 - Ap Su>=1 2 1 D R m 2002 2022 - O lastSu 2 0 S -Z America/Cancun -5:47:4 - LMT 1922 Ja 1 6u --6 - CST 1981 D 23 --5 m E%sT 1998 Au 2 2 --6 m C%sT 2015 F 1 2 --5 - EST -Z America/Merida -5:58:28 - LMT 1922 Ja 1 6u --6 - CST 1981 D 23 --5 - EST 1982 D 2 --6 m C%sT -Z America/Matamoros -6:30 - LMT 1922 Ja 1 6u --6 - CST 1988 --6 u C%sT 1989 --6 m C%sT 2010 --6 u C%sT -Z America/Monterrey -6:41:16 - LMT 1922 Ja 1 6u --6 - CST 1988 --6 u C%sT 1989 --6 m C%sT -Z America/Mexico_City -6:36:36 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 m C%sT 2001 S 30 2 --6 - CST 2002 F 20 --6 m C%sT -Z America/Ciudad_Juarez -7:5:56 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 - CST 1996 --6 m C%sT 1998 --6 - CST 1998 Ap Su>=1 3 --7 m M%sT 2010 --7 u M%sT 2022 O 30 2 --6 - CST 2022 N 30 --7 u M%sT -Z America/Ojinaga -6:57:40 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 - CST 1996 --6 m C%sT 1998 --6 - CST 1998 Ap Su>=1 3 --7 m M%sT 2010 --7 u M%sT 2022 O 30 2 --6 - CST 2022 N 30 --6 u C%sT -Z America/Chihuahua -7:4:20 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 - CST 1996 --6 m C%sT 1998 --6 - CST 1998 Ap Su>=1 3 --7 m M%sT 2022 O 30 2 --6 - CST -Z America/Hermosillo -7:23:52 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 - CST 1942 Ap 24 --7 - MST 1949 Ja 14 --8 - PST 1970 --7 m M%sT 1999 --7 - MST -Z America/Mazatlan -7:5:40 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 - CST 1942 Ap 24 --7 - MST 1949 Ja 14 --8 - PST 1970 --7 m M%sT -Z America/Bahia_Banderas -7:1 - LMT 1922 Ja 1 7u --7 - MST 1927 Jun 10 23 --6 - CST 1930 N 15 --7 m M%sT 1932 Ap --6 - CST 1942 Ap 24 --7 - MST 1949 Ja 14 --8 - PST 1970 --7 m M%sT 2010 Ap 4 2 --6 m C%sT -Z America/Tijuana -7:48:4 - LMT 1922 Ja 1 7u --7 - MST 1924 --8 - PST 1927 Jun 10 23 --7 - MST 1930 N 15 --8 - PST 1931 Ap --8 1 PDT 1931 S 30 --8 - PST 1942 Ap 24 --8 1 PWT 1945 Au 14 23u --8 1 PPT 1945 N 12 --8 - PST 1948 Ap 5 --8 1 PDT 1949 Ja 14 --8 - PST 1954 --8 CA P%sT 1961 --8 - PST 1976 --8 u P%sT 1996 --8 m P%sT 2001 --8 u P%sT 2002 F 20 --8 m P%sT 2010 --8 u P%sT R BB 1942 o - Ap 19 5u 1 D R BB 1942 o - Au 31 6u 0 S R BB 1943 o - May 2 5u 1 D @@ -3294,10 +1755,6 @@ R BB 1978 1980 - Ap Su>=15 2 1 D R BB 1979 o - S 30 2 0 S R BB 1980 o - S 25 2 0 S -Z America/Barbados -3:58:29 - LMT 1911 Au 28 --4 BB A%sT 1944 --4 BB AST/-0330 1945 --4 BB A%sT R BZ 1918 1941 - O Sa>=1 24 0:30 -0530 R BZ 1919 1942 - F Sa>=8 24 0 CST R BZ 1942 o - Jun 27 24 1 CWT @@ -3309,8 +1766,6 @@ R BZ 1974 o - F 9 0 0 CST R BZ 1982 o - D 18 0 1 CDT R BZ 1983 o - F 12 0 0 CST -Z America/Belize -5:52:48 - LMT 1912 Ap --6 BZ %s R Be 1917 o - Ap 5 24 1 - R Be 1917 o - S 30 24 0 - R Be 1918 o - Ap 13 24 1 - @@ -3327,19 +1782,11 @@ R Be 1948 1952 - S Su>=1 2 0 S R Be 1956 o - May Su>=22 2 1 D R Be 1956 o - O lastSu 2 0 S -Z Atlantic/Bermuda -4:19:18 - LMT 1890 --4:19:18 Be BMT/BST 1930 Ja 1 2 --4 Be A%sT 1974 Ap 28 2 --4 C A%sT 1976 --4 u A%sT R CR 1979 1980 - F lastSu 0 1 D R CR 1979 1980 - Jun Su>=1 0 0 S R CR 1991 1992 - Ja Sa>=15 0 1 D R CR 1991 o - Jul 1 0 0 S R CR 1992 o - Mar 15 0 0 S -Z America/Costa_Rica -5:36:13 - LMT 1890 --5:36:13 - SJMT 1921 Ja 15 --6 CR C%sT R Q 1928 o - Jun 10 0 1 D R Q 1928 o - O 10 0 0 S R Q 1940 1942 - Jun Su>=1 0 1 D @@ -3379,25 +1826,14 @@ R Q 2012 o - Ap 1 0s 1 D R Q 2012 ma - N Su>=1 0s 0 S R Q 2013 ma - Mar Su>=8 0s 1 D -Z America/Havana -5:29:28 - LMT 1890 --5:29:36 - HMT 1925 Jul 19 12 --5 Q C%sT R DO 1966 o - O 30 0 1 EDT R DO 1967 o - F 28 0 0 EST R DO 1969 1973 - O lastSu 0 0:30 -0430 R DO 1970 o - F 21 0 0 EST R DO 1971 o - Ja 20 0 0 EST R DO 1972 1974 - Ja 21 0 0 EST -Z America/Santo_Domingo -4:39:36 - LMT 1890 --4:40 - SDMT 1933 Ap 1 12 --5 DO %s 1974 O 27 --4 - AST 2000 O 29 2 --5 u E%sT 2000 D 3 1 --4 - AST R SV 1987 1988 - May Su>=1 0 1 D R SV 1987 1988 - S lastSu 0 0 S -Z America/El_Salvador -5:56:48 - LMT 1921 --6 SV C%sT R GT 1973 o - N 25 0 1 D R GT 1974 o - F 24 0 0 S R GT 1983 o - May 21 0 1 D @@ -3406,8 +1842,6 @@ R GT 1991 o - S 7 0 0 S R GT 2006 o - Ap 30 0 1 D R GT 2006 o - O 1 0 0 S -Z America/Guatemala -6:2:4 - LMT 1918 O 5 --6 GT C%sT R HT 1983 o - May 8 0 1 D R HT 1984 1987 - Ap lastSu 0 1 D R HT 1983 1987 - O lastSu 0 0 S @@ -3419,57 +1853,16 @@ R HT 2012 2015 - N Su>=1 2 0 S R HT 2017 ma - Mar Su>=8 2 1 D R HT 2017 ma - N Su>=1 2 0 S -Z America/Port-au-Prince -4:49:20 - LMT 1890 --4:49 - PPMT 1917 Ja 24 12 --5 HT E%sT R HN 1987 1988 - May Su>=1 0 1 D R HN 1987 1988 - S lastSu 0 0 S R HN 2006 o - May Su>=1 0 1 D R HN 2006 o - Au M>=1 0 0 S -Z America/Tegucigalpa -5:48:52 - LMT 1921 Ap --6 HN C%sT -Z America/Jamaica -5:7:10 - LMT 1890 --5:7:10 - KMT 1912 F --5 - EST 1974 --5 u E%sT 1984 --5 - EST -Z America/Martinique -4:4:20 - LMT 1890 --4:4:20 - FFMT 1911 May --4 - AST 1980 Ap 6 --4 1 ADT 1980 S 28 --4 - AST R NI 1979 1980 - Mar Su>=16 0 1 D R NI 1979 1980 - Jun M>=23 0 0 S R NI 2005 o - Ap 10 0 1 D R NI 2005 o - O Su>=1 0 0 S R NI 2006 o - Ap 30 2 1 D R NI 2006 o - O Su>=1 1 0 S -Z America/Managua -5:45:8 - LMT 1890 --5:45:12 - MMT 1934 Jun 23 --6 - CST 1973 May --5 - EST 1975 F 16 --6 NI C%sT 1992 Ja 1 4 --5 - EST 1992 S 24 --6 - CST 1993 --5 - EST 1997 --6 NI C%sT -Z America/Panama -5:18:8 - LMT 1890 --5:19:36 - CMT 1908 Ap 22 --5 - EST -Z America/Puerto_Rico -4:24:25 - LMT 1899 Mar 28 12 --4 - AST 1942 May 3 --4 u A%sT 1946 --4 - AST -Z America/Miquelon -3:44:40 - LMT 1911 May 15 --4 - AST 1980 May --3 - -03 1987 --3 C -03/-02 -Z America/Grand_Turk -4:44:32 - LMT 1890 --5:7:10 - KMT 1912 F --5 - EST 1979 --5 u E%sT 2015 Mar 8 2 --4 - AST 2018 Mar 11 3 --5 u E%sT R A 1930 o - D 1 0 1 - R A 1931 o - Ap 1 0 0 - R A 1931 o - O 15 0 1 - @@ -3499,150 +1892,8 @@ R A 2007 o - D 30 0 1 - R A 2008 2009 - Mar Su>=15 0 0 - R A 2008 o - O Su>=15 0 1 - -Z America/Argentina/Buenos_Aires -3:53:48 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 A -03/-02 -Z America/Argentina/Cordoba -4:16:48 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1991 Mar 3 --4 - -04 1991 O 20 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 A -03/-02 -Z America/Argentina/Salta -4:21:40 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1991 Mar 3 --4 - -04 1991 O 20 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/Argentina/Tucuman -4:20:52 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1991 Mar 3 --4 - -04 1991 O 20 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 Jun --4 - -04 2004 Jun 13 --3 A -03/-02 -Z America/Argentina/La_Rioja -4:27:24 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1991 Mar --4 - -04 1991 May 7 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 Jun --4 - -04 2004 Jun 20 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/Argentina/San_Juan -4:34:4 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1991 Mar --4 - -04 1991 May 7 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 May 31 --4 - -04 2004 Jul 25 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/Argentina/Jujuy -4:21:12 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1990 Mar 4 --4 - -04 1990 O 28 --4 1 -03 1991 Mar 17 --4 - -04 1991 O 6 --3 1 -02 1992 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/Argentina/Catamarca -4:23:8 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1991 Mar 3 --4 - -04 1991 O 20 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 Jun --4 - -04 2004 Jun 20 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/Argentina/Mendoza -4:35:16 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1990 Mar 4 --4 - -04 1990 O 15 --4 1 -03 1991 Mar --4 - -04 1991 O 15 --4 1 -03 1992 Mar --4 - -04 1992 O 18 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 May 23 --4 - -04 2004 S 26 --3 A -03/-02 2008 O 18 --3 - -03 R Sa 2008 2009 - Mar Su>=8 0 0 - R Sa 2007 2008 - O Su>=8 0 1 - -Z America/Argentina/San_Luis -4:25:24 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1990 --3 1 -02 1990 Mar 14 --4 - -04 1990 O 15 --4 1 -03 1991 Mar --4 - -04 1991 Jun --3 - -03 1999 O 3 --4 1 -03 2000 Mar 3 --3 - -03 2004 May 31 --4 - -04 2004 Jul 25 --3 A -03/-02 2008 Ja 21 --4 Sa -04/-03 2009 O 11 --3 - -03 -Z America/Argentina/Rio_Gallegos -4:36:52 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 Jun --4 - -04 2004 Jun 20 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/Argentina/Ushuaia -4:33:12 - LMT 1894 O 31 --4:16:48 - CMT 1920 May --4 - -04 1930 D --4 A -04/-03 1969 O 5 --3 A -03/-02 1999 O 3 --4 A -04/-03 2000 Mar 3 --3 - -03 2004 May 30 --4 - -04 2004 Jun 20 --3 A -03/-02 2008 O 18 --3 - -03 -Z America/La_Paz -4:32:36 - LMT 1890 --4:32:36 - CMT 1931 O 15 --4:32:36 1 BST 1932 Mar 21 --4 - -04 R B 1931 o - O 3 11 1 - R B 1932 1933 - Ap 1 0 0 - R B 1932 o - O 3 0 1 - @@ -3700,90 +1951,6 @@ R B 2015 o - F Su>=22 0 0 - R B 2016 2019 - F Su>=15 0 0 - R B 2018 o - N Su>=1 0 1 - -Z America/Noronha -2:9:40 - LMT 1914 --2 B -02/-01 1990 S 17 --2 - -02 1999 S 30 --2 B -02/-01 2000 O 15 --2 - -02 2001 S 13 --2 B -02/-01 2002 O --2 - -02 -Z America/Belem -3:13:56 - LMT 1914 --3 B -03/-02 1988 S 12 --3 - -03 -Z America/Santarem -3:38:48 - LMT 1914 --4 B -04/-03 1988 S 12 --4 - -04 2008 Jun 24 --3 - -03 -Z America/Fortaleza -2:34 - LMT 1914 --3 B -03/-02 1990 S 17 --3 - -03 1999 S 30 --3 B -03/-02 2000 O 22 --3 - -03 2001 S 13 --3 B -03/-02 2002 O --3 - -03 -Z America/Recife -2:19:36 - LMT 1914 --3 B -03/-02 1990 S 17 --3 - -03 1999 S 30 --3 B -03/-02 2000 O 15 --3 - -03 2001 S 13 --3 B -03/-02 2002 O --3 - -03 -Z America/Araguaina -3:12:48 - LMT 1914 --3 B -03/-02 1990 S 17 --3 - -03 1995 S 14 --3 B -03/-02 2003 S 24 --3 - -03 2012 O 21 --3 B -03/-02 2013 S --3 - -03 -Z America/Maceio -2:22:52 - LMT 1914 --3 B -03/-02 1990 S 17 --3 - -03 1995 O 13 --3 B -03/-02 1996 S 4 --3 - -03 1999 S 30 --3 B -03/-02 2000 O 22 --3 - -03 2001 S 13 --3 B -03/-02 2002 O --3 - -03 -Z America/Bahia -2:34:4 - LMT 1914 --3 B -03/-02 2003 S 24 --3 - -03 2011 O 16 --3 B -03/-02 2012 O 21 --3 - -03 -Z America/Sao_Paulo -3:6:28 - LMT 1914 --3 B -03/-02 1963 O 23 --3 1 -02 1964 --3 B -03/-02 -Z America/Campo_Grande -3:38:28 - LMT 1914 --4 B -04/-03 -Z America/Cuiaba -3:44:20 - LMT 1914 --4 B -04/-03 2003 S 24 --4 - -04 2004 O --4 B -04/-03 -Z America/Porto_Velho -4:15:36 - LMT 1914 --4 B -04/-03 1988 S 12 --4 - -04 -Z America/Boa_Vista -4:2:40 - LMT 1914 --4 B -04/-03 1988 S 12 --4 - -04 1999 S 30 --4 B -04/-03 2000 O 15 --4 - -04 -Z America/Manaus -4:0:4 - LMT 1914 --4 B -04/-03 1988 S 12 --4 - -04 1993 S 28 --4 B -04/-03 1994 S 22 --4 - -04 -Z America/Eirunepe -4:39:28 - LMT 1914 --5 B -05/-04 1988 S 12 --5 - -05 1993 S 28 --5 B -05/-04 1994 S 22 --5 - -05 2008 Jun 24 --4 - -04 2013 N 10 --5 - -05 -Z America/Rio_Branco -4:31:12 - LMT 1914 --5 B -05/-04 1988 S 12 --5 - -05 2008 Jun 24 --4 - -04 2013 N 10 --5 - -05 R x 1927 1931 - S 1 0 1 - R x 1928 1932 - Ap 1 0 0 - R x 1968 o - N 3 4u 1 - @@ -3820,56 +1987,10 @@ R x 2019 2021 - S Su>=2 4u 1 - R x 2022 o - S Su>=9 4u 1 - R x 2023 ma - S Su>=2 4u 1 - -Z America/Santiago -4:42:45 - LMT 1890 --4:42:45 - SMT 1910 Ja 10 --5 - -05 1916 Jul --4:42:45 - SMT 1918 S 10 --4 - -04 1919 Jul --4:42:45 - SMT 1927 S --5 x -05/-04 1932 S --4 - -04 1942 Jun --5 - -05 1942 Au --4 - -04 1946 Jul 14 24 --4 1 -03 1946 Au 28 24 --5 1 -04 1947 Mar 31 24 --5 - -05 1947 May 21 23 --4 x -04/-03 -Z America/Punta_Arenas -4:43:40 - LMT 1890 --4:42:45 - SMT 1910 Ja 10 --5 - -05 1916 Jul --4:42:45 - SMT 1918 S 10 --4 - -04 1919 Jul --4:42:45 - SMT 1927 S --5 x -05/-04 1932 S --4 - -04 1942 Jun --5 - -05 1942 Au --4 - -04 1946 Au 28 24 --5 1 -04 1947 Mar 31 24 --5 - -05 1947 May 21 23 --4 x -04/-03 2016 D 4 --3 - -03 -Z Pacific/Easter -7:17:28 - LMT 1890 --7:17:28 - EMT 1932 S --7 x -07/-06 1982 Mar 14 3u --6 x -06/-05 -Z Antarctica/Palmer 0 - -00 1965 --4 A -04/-03 1969 O 5 --3 A -03/-02 1982 May --4 x -04/-03 2016 D 4 --3 - -03 R CO 1992 o - May 3 0 1 - R CO 1993 o - F 6 24 0 - -Z America/Bogota -4:56:16 - LMT 1884 Mar 13 --4:56:16 - BMT 1914 N 23 --5 CO -05/-04 R EC 1992 o - N 28 0 1 - R EC 1993 o - F 5 0 0 - -Z America/Guayaquil -5:19:20 - LMT 1890 --5:14 - QMT 1931 --5 EC -05/-04 -Z Pacific/Galapagos -5:58:24 - LMT 1931 --5 - -05 1986 --6 EC -06/-05 R FK 1937 1938 - S lastSu 0 1 - R FK 1938 1942 - Mar Su>=19 0 0 - R FK 1939 o - O 1 0 1 - @@ -3882,20 +2003,6 @@ R FK 1986 2000 - Ap Su>=16 0 0 - R FK 2001 2010 - Ap Su>=15 2 0 - R FK 2001 2010 - S Su>=1 2 1 - -Z Atlantic/Stanley -3:51:24 - LMT 1890 --3:51:24 - SMT 1912 Mar 12 --4 FK -04/-03 1983 May --3 FK -03/-02 1985 S 15 --4 FK -04/-03 2010 S 5 2 --3 - -03 -Z America/Cayenne -3:29:20 - LMT 1911 Jul --4 - -04 1967 O --3 - -03 -Z America/Guyana -3:52:39 - LMT 1911 Au --4 - -04 1915 Mar --3:45 - -0345 1975 Au --3 - -03 1992 Mar 29 1 --4 - -04 R y 1975 1988 - O 1 0 1 - R y 1975 1978 - Mar 1 0 0 - R y 1979 1991 - Ap 1 0 0 - @@ -3918,11 +2025,6 @@ R y 2010 ma - O Su>=1 0 1 - R y 2010 2012 - Ap Su>=8 0 0 - R y 2013 ma - Mar Su>=22 0 0 - -Z America/Asuncion -3:50:40 - LMT 1890 --3:50:40 - AMT 1931 O 10 --4 - -04 1972 O --3 - -03 1974 Ap --4 y -04/-03 R PE 1938 o - Ja 1 0 1 - R PE 1938 o - Ap 1 0 0 - R PE 1938 1939 - S lastSu 0 1 - @@ -3933,16 +2035,6 @@ R PE 1990 o - Ap 1 0 0 - R PE 1994 o - Ja 1 0 1 - R PE 1994 o - Ap 1 0 0 - -Z America/Lima -5:8:12 - LMT 1890 --5:8:36 - LMT 1908 Jul 28 --5 PE -05/-04 -Z Atlantic/South_Georgia -2:26:8 - LMT 1890 --2 - -02 -Z America/Paramaribo -3:40:40 - LMT 1911 --3:40:52 - PMT 1935 --3:40:36 - PMT 1945 O --3:30 - -0330 1984 O --3 - -03 R U 1923 1925 - O 1 0 0:30 - R U 1924 1926 - Ap 1 0 0 - R U 1933 1938 - O lastSu 0 0:30 - @@ -3991,6 +2083,659 @@ R U 2005 o - O 9 2 1 - R U 2006 2015 - Mar Su>=8 2 0 - R U 2006 2014 - O Su>=1 2 1 - +Z Africa/Abidjan -0:16:8 - LMT 1912 +0 - GMT +Z Africa/Algiers 0:12:12 - LMT 1891 Mar 16 +0:9:21 - PMT 1911 Mar 11 +0 d WE%sT 1940 F 25 2 +1 d CE%sT 1946 O 7 +0 - WET 1956 Ja 29 +1 - CET 1963 Ap 14 +0 d WE%sT 1977 O 21 +1 d CE%sT 1979 O 26 +0 d WE%sT 1981 May +1 - CET +Z Africa/Bissau -1:2:20 - LMT 1912 Ja 1 1u +-1 - -01 1975 +0 - GMT +Z Africa/Cairo 2:5:9 - LMT 1900 O +2 K EE%sT +Z Africa/Casablanca -0:30:20 - LMT 1913 O 26 +0 M +00/+01 1984 Mar 16 +1 - +01 1986 +0 M +00/+01 2018 O 28 3 +1 M +01/+00 +Z Africa/Ceuta -0:21:16 - LMT 1901 Ja 1 0u +0 - WET 1918 May 6 23 +0 1 WEST 1918 O 7 23 +0 - WET 1924 +0 s WE%sT 1929 +0 - WET 1967 +0 Sp WE%sT 1984 Mar 16 +1 - CET 1986 +1 E CE%sT +Z Africa/El_Aaiun -0:52:48 - LMT 1934 +-1 - -01 1976 Ap 14 +0 M +00/+01 2018 O 28 3 +1 M +01/+00 +Z Africa/Johannesburg 1:52 - LMT 1892 F 8 +1:30 - SAST 1903 Mar +2 SA SAST +Z Africa/Juba 2:6:28 - LMT 1931 +2 SD CA%sT 2000 Ja 15 12 +3 - EAT 2021 F +2 - CAT +Z Africa/Khartoum 2:10:8 - LMT 1931 +2 SD CA%sT 2000 Ja 15 12 +3 - EAT 2017 N +2 - CAT +Z Africa/Lagos 0:13:35 - LMT 1905 Jul +0 - GMT 1908 Jul +0:13:35 - LMT 1914 +0:30 - +0030 1919 S +1 - WAT +Z Africa/Maputo 2:10:20 - LMT 1903 Mar +2 - CAT +Z Africa/Monrovia -0:43:8 - LMT 1882 +-0:43:8 - MMT 1919 Mar +-0:44:30 - MMT 1972 Ja 7 +0 - GMT +Z Africa/Nairobi 2:27:16 - LMT 1908 May +2:30 - +0230 1928 Jun 30 24 +3 - EAT 1930 Ja 4 24 +2:30 - +0230 1936 D 31 24 +2:45 - +0245 1942 Jul 31 24 +3 - EAT +Z Africa/Ndjamena 1:0:12 - LMT 1912 +1 - WAT 1979 O 14 +1 1 WAST 1980 Mar 8 +1 - WAT +Z Africa/Sao_Tome 0:26:56 - LMT 1884 +-0:36:45 - LMT 1912 Ja 1 0u +0 - GMT 2018 Ja 1 1 +1 - WAT 2019 Ja 1 2 +0 - GMT +Z Africa/Tripoli 0:52:44 - LMT 1920 +1 L CE%sT 1959 +2 - EET 1982 +1 L CE%sT 1990 May 4 +2 - EET 1996 S 30 +1 L CE%sT 1997 O 4 +2 - EET 2012 N 10 2 +1 L CE%sT 2013 O 25 2 +2 - EET +Z Africa/Tunis 0:40:44 - LMT 1881 May 12 +0:9:21 - PMT 1911 Mar 11 +1 n CE%sT +Z Africa/Windhoek 1:8:24 - LMT 1892 F 8 +1:30 - +0130 1903 Mar +2 - SAST 1942 S 20 2 +2 1 SAST 1943 Mar 21 2 +2 - SAST 1990 Mar 21 +2 NA %s +Z America/Adak 12:13:22 - LMT 1867 O 19 12:44:35 +-11:46:38 - LMT 1900 Au 20 12 +-11 - NST 1942 +-11 u N%sT 1946 +-11 - NST 1967 Ap +-11 - BST 1969 +-11 u B%sT 1983 O 30 2 +-10 u AH%sT 1983 N 30 +-10 u H%sT +Z America/Anchorage 14:0:24 - LMT 1867 O 19 14:31:37 +-9:59:36 - LMT 1900 Au 20 12 +-10 - AST 1942 +-10 u A%sT 1967 Ap +-10 - AHST 1969 +-10 u AH%sT 1983 O 30 2 +-9 u Y%sT 1983 N 30 +-9 u AK%sT +Z America/Araguaina -3:12:48 - LMT 1914 +-3 B -03/-02 1990 S 17 +-3 - -03 1995 S 14 +-3 B -03/-02 2003 S 24 +-3 - -03 2012 O 21 +-3 B -03/-02 2013 S +-3 - -03 +Z America/Argentina/Buenos_Aires -3:53:48 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 A -03/-02 +Z America/Argentina/Catamarca -4:23:8 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1991 Mar 3 +-4 - -04 1991 O 20 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 Jun +-4 - -04 2004 Jun 20 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/Cordoba -4:16:48 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1991 Mar 3 +-4 - -04 1991 O 20 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 A -03/-02 +Z America/Argentina/Jujuy -4:21:12 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1990 Mar 4 +-4 - -04 1990 O 28 +-4 1 -03 1991 Mar 17 +-4 - -04 1991 O 6 +-3 1 -02 1992 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/La_Rioja -4:27:24 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1991 Mar +-4 - -04 1991 May 7 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 Jun +-4 - -04 2004 Jun 20 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/Mendoza -4:35:16 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1990 Mar 4 +-4 - -04 1990 O 15 +-4 1 -03 1991 Mar +-4 - -04 1991 O 15 +-4 1 -03 1992 Mar +-4 - -04 1992 O 18 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 May 23 +-4 - -04 2004 S 26 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/Rio_Gallegos -4:36:52 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 Jun +-4 - -04 2004 Jun 20 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/Salta -4:21:40 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1991 Mar 3 +-4 - -04 1991 O 20 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/San_Juan -4:34:4 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1991 Mar +-4 - -04 1991 May 7 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 May 31 +-4 - -04 2004 Jul 25 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Argentina/San_Luis -4:25:24 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1990 +-3 1 -02 1990 Mar 14 +-4 - -04 1990 O 15 +-4 1 -03 1991 Mar +-4 - -04 1991 Jun +-3 - -03 1999 O 3 +-4 1 -03 2000 Mar 3 +-3 - -03 2004 May 31 +-4 - -04 2004 Jul 25 +-3 A -03/-02 2008 Ja 21 +-4 Sa -04/-03 2009 O 11 +-3 - -03 +Z America/Argentina/Tucuman -4:20:52 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1991 Mar 3 +-4 - -04 1991 O 20 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 Jun +-4 - -04 2004 Jun 13 +-3 A -03/-02 +Z America/Argentina/Ushuaia -4:33:12 - LMT 1894 O 31 +-4:16:48 - CMT 1920 May +-4 - -04 1930 D +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1999 O 3 +-4 A -04/-03 2000 Mar 3 +-3 - -03 2004 May 30 +-4 - -04 2004 Jun 20 +-3 A -03/-02 2008 O 18 +-3 - -03 +Z America/Asuncion -3:50:40 - LMT 1890 +-3:50:40 - AMT 1931 O 10 +-4 - -04 1972 O +-3 - -03 1974 Ap +-4 y -04/-03 +Z America/Bahia -2:34:4 - LMT 1914 +-3 B -03/-02 2003 S 24 +-3 - -03 2011 O 16 +-3 B -03/-02 2012 O 21 +-3 - -03 +Z America/Bahia_Banderas -7:1 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 - CST 1942 Ap 24 +-7 - MST 1949 Ja 14 +-8 - PST 1970 +-7 m M%sT 2010 Ap 4 2 +-6 m C%sT +Z America/Barbados -3:58:29 - LMT 1911 Au 28 +-4 BB A%sT 1944 +-4 BB AST/-0330 1945 +-4 BB A%sT +Z America/Belem -3:13:56 - LMT 1914 +-3 B -03/-02 1988 S 12 +-3 - -03 +Z America/Belize -5:52:48 - LMT 1912 Ap +-6 BZ %s +Z America/Boa_Vista -4:2:40 - LMT 1914 +-4 B -04/-03 1988 S 12 +-4 - -04 1999 S 30 +-4 B -04/-03 2000 O 15 +-4 - -04 +Z America/Bogota -4:56:16 - LMT 1884 Mar 13 +-4:56:16 - BMT 1914 N 23 +-5 CO -05/-04 +Z America/Boise -7:44:49 - LMT 1883 N 18 20u +-8 u P%sT 1923 May 13 2 +-7 u M%sT 1974 +-7 - MST 1974 F 3 2 +-7 u M%sT +Z America/Cambridge_Bay 0 - -00 1920 +-7 Y M%sT 1999 O 31 2 +-6 C C%sT 2000 O 29 2 +-5 - EST 2000 N 5 +-6 - CST 2001 Ap 1 3 +-7 C M%sT +Z America/Campo_Grande -3:38:28 - LMT 1914 +-4 B -04/-03 +Z America/Cancun -5:47:4 - LMT 1922 Ja 1 6u +-6 - CST 1981 D 23 +-5 m E%sT 1998 Au 2 2 +-6 m C%sT 2015 F 1 2 +-5 - EST +Z America/Caracas -4:27:44 - LMT 1890 +-4:27:40 - CMT 1912 F 12 +-4:30 - -0430 1965 +-4 - -04 2007 D 9 3 +-4:30 - -0430 2016 May 1 2:30 +-4 - -04 +Z America/Cayenne -3:29:20 - LMT 1911 Jul +-4 - -04 1967 O +-3 - -03 +Z America/Chicago -5:50:36 - LMT 1883 N 18 18u +-6 u C%sT 1920 +-6 Ch C%sT 1936 Mar 1 2 +-5 - EST 1936 N 15 2 +-6 Ch C%sT 1942 +-6 u C%sT 1946 +-6 Ch C%sT 1967 +-6 u C%sT +Z America/Chihuahua -7:4:20 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 - CST 1996 +-6 m C%sT 1998 +-6 - CST 1998 Ap Su>=1 3 +-7 m M%sT 2022 O 30 2 +-6 - CST +Z America/Ciudad_Juarez -7:5:56 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 - CST 1996 +-6 m C%sT 1998 +-6 - CST 1998 Ap Su>=1 3 +-7 m M%sT 2010 +-7 u M%sT 2022 O 30 2 +-6 - CST 2022 N 30 +-7 u M%sT +Z America/Costa_Rica -5:36:13 - LMT 1890 +-5:36:13 - SJMT 1921 Ja 15 +-6 CR C%sT +Z America/Cuiaba -3:44:20 - LMT 1914 +-4 B -04/-03 2003 S 24 +-4 - -04 2004 O +-4 B -04/-03 +Z America/Danmarkshavn -1:14:40 - LMT 1916 Jul 28 +-3 - -03 1980 Ap 6 2 +-3 E -03/-02 1996 +0 - GMT +Z America/Dawson -9:17:40 - LMT 1900 Au 20 +-9 Y Y%sT 1965 +-9 Yu Y%sT 1973 O 28 +-8 - PST 1980 +-8 C P%sT 2020 N +-7 - MST +Z America/Dawson_Creek -8:0:56 - LMT 1884 +-8 C P%sT 1947 +-8 Va P%sT 1972 Au 30 2 +-7 - MST +Z America/Denver -6:59:56 - LMT 1883 N 18 19u +-7 u M%sT 1920 +-7 De M%sT 1942 +-7 u M%sT 1946 +-7 De M%sT 1967 +-7 u M%sT +Z America/Detroit -5:32:11 - LMT 1905 +-6 - CST 1915 May 15 2 +-5 - EST 1942 +-5 u E%sT 1946 +-5 Dt E%sT 1967 Jun 14 0:1 +-5 u E%sT 1969 +-5 - EST 1973 +-5 u E%sT 1975 +-5 - EST 1975 Ap 27 2 +-5 u E%sT +Z America/Edmonton -7:33:52 - LMT 1906 S +-7 Ed M%sT 1987 +-7 C M%sT +Z America/Eirunepe -4:39:28 - LMT 1914 +-5 B -05/-04 1988 S 12 +-5 - -05 1993 S 28 +-5 B -05/-04 1994 S 22 +-5 - -05 2008 Jun 24 +-4 - -04 2013 N 10 +-5 - -05 +Z America/El_Salvador -5:56:48 - LMT 1921 +-6 SV C%sT +Z America/Fort_Nelson -8:10:47 - LMT 1884 +-8 Va P%sT 1946 +-8 - PST 1947 +-8 Va P%sT 1987 +-8 C P%sT 2015 Mar 8 2 +-7 - MST +Z America/Fortaleza -2:34 - LMT 1914 +-3 B -03/-02 1990 S 17 +-3 - -03 1999 S 30 +-3 B -03/-02 2000 O 22 +-3 - -03 2001 S 13 +-3 B -03/-02 2002 O +-3 - -03 +Z America/Glace_Bay -3:59:48 - LMT 1902 Jun 15 +-4 C A%sT 1953 +-4 H A%sT 1954 +-4 - AST 1972 +-4 H A%sT 1974 +-4 C A%sT +Z America/Goose_Bay -4:1:40 - LMT 1884 +-3:30:52 - NST 1918 +-3:30:52 C N%sT 1919 +-3:30:52 - NST 1935 Mar 30 +-3:30 - NST 1936 +-3:30 j N%sT 1942 May 11 +-3:30 C N%sT 1946 +-3:30 j N%sT 1966 Mar 15 2 +-4 j A%sT 2011 N +-4 C A%sT +Z America/Grand_Turk -4:44:32 - LMT 1890 +-5:7:10 - KMT 1912 F +-5 - EST 1979 +-5 u E%sT 2015 Mar 8 2 +-4 - AST 2018 Mar 11 3 +-5 u E%sT +Z America/Guatemala -6:2:4 - LMT 1918 O 5 +-6 GT C%sT +Z America/Guayaquil -5:19:20 - LMT 1890 +-5:14 - QMT 1931 +-5 EC -05/-04 +Z America/Guyana -3:52:39 - LMT 1911 Au +-4 - -04 1915 Mar +-3:45 - -0345 1975 Au +-3 - -03 1992 Mar 29 1 +-4 - -04 +Z America/Halifax -4:14:24 - LMT 1902 Jun 15 +-4 H A%sT 1918 +-4 C A%sT 1919 +-4 H A%sT 1942 F 9 2s +-4 C A%sT 1946 +-4 H A%sT 1974 +-4 C A%sT +Z America/Havana -5:29:28 - LMT 1890 +-5:29:36 - HMT 1925 Jul 19 12 +-5 Q C%sT +Z America/Hermosillo -7:23:52 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 - CST 1942 Ap 24 +-7 - MST 1949 Ja 14 +-8 - PST 1970 +-7 m M%sT 1999 +-7 - MST +Z America/Indiana/Indianapolis -5:44:38 - LMT 1883 N 18 18u +-6 u C%sT 1920 +-6 In C%sT 1942 +-6 u C%sT 1946 +-6 In C%sT 1955 Ap 24 2 +-5 - EST 1957 S 29 2 +-6 - CST 1958 Ap 27 2 +-5 - EST 1969 +-5 u E%sT 1971 +-5 - EST 2006 +-5 u E%sT +Z America/Indiana/Knox -5:46:30 - LMT 1883 N 18 18u +-6 u C%sT 1947 +-6 St C%sT 1962 Ap 29 2 +-5 - EST 1963 O 27 2 +-6 u C%sT 1991 O 27 2 +-5 - EST 2006 Ap 2 2 +-6 u C%sT +Z America/Indiana/Marengo -5:45:23 - LMT 1883 N 18 18u +-6 u C%sT 1951 +-6 Ma C%sT 1961 Ap 30 2 +-5 - EST 1969 +-5 u E%sT 1974 Ja 6 2 +-6 1 CDT 1974 O 27 2 +-5 u E%sT 1976 +-5 - EST 2006 +-5 u E%sT +Z America/Indiana/Petersburg -5:49:7 - LMT 1883 N 18 18u +-6 u C%sT 1955 +-6 Pi C%sT 1965 Ap 25 2 +-5 - EST 1966 O 30 2 +-6 u C%sT 1977 O 30 2 +-5 - EST 2006 Ap 2 2 +-6 u C%sT 2007 N 4 2 +-5 u E%sT +Z America/Indiana/Tell_City -5:47:3 - LMT 1883 N 18 18u +-6 u C%sT 1946 +-6 Pe C%sT 1964 Ap 26 2 +-5 - EST 1967 O 29 2 +-6 u C%sT 1969 Ap 27 2 +-5 u E%sT 1971 +-5 - EST 2006 Ap 2 2 +-6 u C%sT +Z America/Indiana/Vevay -5:40:16 - LMT 1883 N 18 18u +-6 u C%sT 1954 Ap 25 2 +-5 - EST 1969 +-5 u E%sT 1973 +-5 - EST 2006 +-5 u E%sT +Z America/Indiana/Vincennes -5:50:7 - LMT 1883 N 18 18u +-6 u C%sT 1946 +-6 V C%sT 1964 Ap 26 2 +-5 - EST 1969 +-5 u E%sT 1971 +-5 - EST 2006 Ap 2 2 +-6 u C%sT 2007 N 4 2 +-5 u E%sT +Z America/Indiana/Winamac -5:46:25 - LMT 1883 N 18 18u +-6 u C%sT 1946 +-6 Pu C%sT 1961 Ap 30 2 +-5 - EST 1969 +-5 u E%sT 1971 +-5 - EST 2006 Ap 2 2 +-6 u C%sT 2007 Mar 11 2 +-5 u E%sT +Z America/Inuvik 0 - -00 1953 +-8 Y P%sT 1979 Ap lastSu 2 +-7 Y M%sT 1980 +-7 C M%sT +Z America/Iqaluit 0 - -00 1942 Au +-5 Y E%sT 1999 O 31 2 +-6 C C%sT 2000 O 29 2 +-5 C E%sT +Z America/Jamaica -5:7:10 - LMT 1890 +-5:7:10 - KMT 1912 F +-5 - EST 1974 +-5 u E%sT 1984 +-5 - EST +Z America/Juneau 15:2:19 - LMT 1867 O 19 15:33:32 +-8:57:41 - LMT 1900 Au 20 12 +-8 - PST 1942 +-8 u P%sT 1946 +-8 - PST 1969 +-8 u P%sT 1980 Ap 27 2 +-9 u Y%sT 1980 O 26 2 +-8 u P%sT 1983 O 30 2 +-9 u Y%sT 1983 N 30 +-9 u AK%sT +Z America/Kentucky/Louisville -5:43:2 - LMT 1883 N 18 18u +-6 u C%sT 1921 +-6 v C%sT 1942 +-6 u C%sT 1946 +-6 v C%sT 1961 Jul 23 2 +-5 - EST 1968 +-5 u E%sT 1974 Ja 6 2 +-6 1 CDT 1974 O 27 2 +-5 u E%sT +Z America/Kentucky/Monticello -5:39:24 - LMT 1883 N 18 18u +-6 u C%sT 1946 +-6 - CST 1968 +-6 u C%sT 2000 O 29 2 +-5 u E%sT +Z America/La_Paz -4:32:36 - LMT 1890 +-4:32:36 - CMT 1931 O 15 +-4:32:36 1 BST 1932 Mar 21 +-4 - -04 +Z America/Lima -5:8:12 - LMT 1890 +-5:8:36 - LMT 1908 Jul 28 +-5 PE -05/-04 +Z America/Los_Angeles -7:52:58 - LMT 1883 N 18 20u +-8 u P%sT 1946 +-8 CA P%sT 1967 +-8 u P%sT +Z America/Maceio -2:22:52 - LMT 1914 +-3 B -03/-02 1990 S 17 +-3 - -03 1995 O 13 +-3 B -03/-02 1996 S 4 +-3 - -03 1999 S 30 +-3 B -03/-02 2000 O 22 +-3 - -03 2001 S 13 +-3 B -03/-02 2002 O +-3 - -03 +Z America/Managua -5:45:8 - LMT 1890 +-5:45:12 - MMT 1934 Jun 23 +-6 - CST 1973 May +-5 - EST 1975 F 16 +-6 NI C%sT 1992 Ja 1 4 +-5 - EST 1992 S 24 +-6 - CST 1993 +-5 - EST 1997 +-6 NI C%sT +Z America/Manaus -4:0:4 - LMT 1914 +-4 B -04/-03 1988 S 12 +-4 - -04 1993 S 28 +-4 B -04/-03 1994 S 22 +-4 - -04 +Z America/Martinique -4:4:20 - LMT 1890 +-4:4:20 - FFMT 1911 May +-4 - AST 1980 Ap 6 +-4 1 ADT 1980 S 28 +-4 - AST +Z America/Matamoros -6:30 - LMT 1922 Ja 1 6u +-6 - CST 1988 +-6 u C%sT 1989 +-6 m C%sT 2010 +-6 u C%sT +Z America/Mazatlan -7:5:40 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 - CST 1942 Ap 24 +-7 - MST 1949 Ja 14 +-8 - PST 1970 +-7 m M%sT +Z America/Menominee -5:50:27 - LMT 1885 S 18 12 +-6 u C%sT 1946 +-6 Me C%sT 1969 Ap 27 2 +-5 - EST 1973 Ap 29 2 +-6 u C%sT +Z America/Merida -5:58:28 - LMT 1922 Ja 1 6u +-6 - CST 1981 D 23 +-5 - EST 1982 D 2 +-6 m C%sT +Z America/Metlakatla 15:13:42 - LMT 1867 O 19 15:44:55 +-8:46:18 - LMT 1900 Au 20 12 +-8 - PST 1942 +-8 u P%sT 1946 +-8 - PST 1969 +-8 u P%sT 1983 O 30 2 +-8 - PST 2015 N 1 2 +-9 u AK%sT 2018 N 4 2 +-8 - PST 2019 Ja 20 2 +-9 u AK%sT +Z America/Mexico_City -6:36:36 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 m C%sT 2001 S 30 2 +-6 - CST 2002 F 20 +-6 m C%sT +Z America/Miquelon -3:44:40 - LMT 1911 Jun 15 +-4 - AST 1980 May +-3 - -03 1987 +-3 C -03/-02 +Z America/Moncton -4:19:8 - LMT 1883 D 9 +-5 - EST 1902 Jun 15 +-4 C A%sT 1933 +-4 o A%sT 1942 +-4 C A%sT 1946 +-4 o A%sT 1973 +-4 C A%sT 1993 +-4 o A%sT 2007 +-4 C A%sT +Z America/Monterrey -6:41:16 - LMT 1922 Ja 1 6u +-6 - CST 1988 +-6 u C%sT 1989 +-6 m C%sT Z America/Montevideo -3:44:51 - LMT 1908 Jun 10 -3:44:51 - MMT 1920 May -4 - -04 1923 O @@ -4002,30 +2747,842 @@ -3 U -03/-0130 1974 Mar 10 -3 U -03/-0230 1974 D 22 -3 U -03/-02 -Z America/Caracas -4:27:44 - LMT 1890 --4:27:40 - CMT 1912 F 12 --4:30 - -0430 1965 --4 - -04 2007 D 9 3 --4:30 - -0430 2016 May 1 2:30 +Z America/New_York -4:56:2 - LMT 1883 N 18 17u +-5 u E%sT 1920 +-5 NY E%sT 1942 +-5 u E%sT 1946 +-5 NY E%sT 1967 +-5 u E%sT +Z America/Nome 12:58:22 - LMT 1867 O 19 13:29:35 +-11:1:38 - LMT 1900 Au 20 12 +-11 - NST 1942 +-11 u N%sT 1946 +-11 - NST 1967 Ap +-11 - BST 1969 +-11 u B%sT 1983 O 30 2 +-9 u Y%sT 1983 N 30 +-9 u AK%sT +Z America/Noronha -2:9:40 - LMT 1914 +-2 B -02/-01 1990 S 17 +-2 - -02 1999 S 30 +-2 B -02/-01 2000 O 15 +-2 - -02 2001 S 13 +-2 B -02/-01 2002 O +-2 - -02 +Z America/North_Dakota/Beulah -6:47:7 - LMT 1883 N 18 19u +-7 u M%sT 2010 N 7 2 +-6 u C%sT +Z America/North_Dakota/Center -6:45:12 - LMT 1883 N 18 19u +-7 u M%sT 1992 O 25 2 +-6 u C%sT +Z America/North_Dakota/New_Salem -6:45:39 - LMT 1883 N 18 19u +-7 u M%sT 2003 O 26 2 +-6 u C%sT +Z America/Nuuk -3:26:56 - LMT 1916 Jul 28 +-3 - -03 1980 Ap 6 2 +-3 E -03/-02 2023 Mar 26 1u +-2 - -02 2023 O 29 1u +-2 E -02/-01 +Z America/Ojinaga -6:57:40 - LMT 1922 Ja 1 7u +-7 - MST 1927 Jun 10 23 +-6 - CST 1930 N 15 +-7 m M%sT 1932 Ap +-6 - CST 1996 +-6 m C%sT 1998 +-6 - CST 1998 Ap Su>=1 3 +-7 m M%sT 2010 +-7 u M%sT 2022 O 30 2 +-6 - CST 2022 N 30 +-6 u C%sT +Z America/Panama -5:18:8 - LMT 1890 +-5:19:36 - CMT 1908 Ap 22 +-5 - EST +Z America/Paramaribo -3:40:40 - LMT 1911 +-3:40:52 - PMT 1935 +-3:40:36 - PMT 1945 O +-3:30 - -0330 1984 O +-3 - -03 +Z America/Phoenix -7:28:18 - LMT 1883 N 18 19u +-7 u M%sT 1944 Ja 1 0:1 +-7 - MST 1944 Ap 1 0:1 +-7 u M%sT 1944 O 1 0:1 +-7 - MST 1967 +-7 u M%sT 1968 Mar 21 +-7 - MST +Z America/Port-au-Prince -4:49:20 - LMT 1890 +-4:49 - PPMT 1917 Ja 24 12 +-5 HT E%sT +Z America/Porto_Velho -4:15:36 - LMT 1914 +-4 B -04/-03 1988 S 12 -4 - -04 -Z Etc/UTC 0 - UTC +Z America/Puerto_Rico -4:24:25 - LMT 1899 Mar 28 12 +-4 - AST 1942 May 3 +-4 u A%sT 1946 +-4 - AST +Z America/Punta_Arenas -4:43:40 - LMT 1890 +-4:42:45 - SMT 1910 Ja 10 +-5 - -05 1916 Jul +-4:42:45 - SMT 1918 S 10 +-4 - -04 1919 Jul +-4:42:45 - SMT 1927 S +-5 x -05/-04 1932 S +-4 - -04 1942 Jun +-5 - -05 1942 Au +-4 - -04 1946 Au 28 24 +-5 1 -04 1947 Mar 31 24 +-5 - -05 1947 May 21 23 +-4 x -04/-03 2016 D 4 +-3 - -03 +Z America/Rankin_Inlet 0 - -00 1957 +-6 Y C%sT 2000 O 29 2 +-5 - EST 2001 Ap 1 3 +-6 C C%sT +Z America/Recife -2:19:36 - LMT 1914 +-3 B -03/-02 1990 S 17 +-3 - -03 1999 S 30 +-3 B -03/-02 2000 O 15 +-3 - -03 2001 S 13 +-3 B -03/-02 2002 O +-3 - -03 +Z America/Regina -6:58:36 - LMT 1905 S +-7 r M%sT 1960 Ap lastSu 2 +-6 - CST +Z America/Resolute 0 - -00 1947 Au 31 +-6 Y C%sT 2000 O 29 2 +-5 - EST 2001 Ap 1 3 +-6 C C%sT 2006 O 29 2 +-5 - EST 2007 Mar 11 3 +-6 C C%sT +Z America/Rio_Branco -4:31:12 - LMT 1914 +-5 B -05/-04 1988 S 12 +-5 - -05 2008 Jun 24 +-4 - -04 2013 N 10 +-5 - -05 +Z America/Santarem -3:38:48 - LMT 1914 +-4 B -04/-03 1988 S 12 +-4 - -04 2008 Jun 24 +-3 - -03 +Z America/Santiago -4:42:45 - LMT 1890 +-4:42:45 - SMT 1910 Ja 10 +-5 - -05 1916 Jul +-4:42:45 - SMT 1918 S 10 +-4 - -04 1919 Jul +-4:42:45 - SMT 1927 S +-5 x -05/-04 1932 S +-4 - -04 1942 Jun +-5 - -05 1942 Au +-4 - -04 1946 Jul 14 24 +-4 1 -03 1946 Au 28 24 +-5 1 -04 1947 Mar 31 24 +-5 - -05 1947 May 21 23 +-4 x -04/-03 +Z America/Santo_Domingo -4:39:36 - LMT 1890 +-4:40 - SDMT 1933 Ap 1 12 +-5 DO %s 1974 O 27 +-4 - AST 2000 O 29 2 +-5 u E%sT 2000 D 3 1 +-4 - AST +Z America/Sao_Paulo -3:6:28 - LMT 1914 +-3 B -03/-02 1963 O 23 +-3 1 -02 1964 +-3 B -03/-02 +Z America/Scoresbysund -1:27:52 - LMT 1916 Jul 28 +-2 - -02 1980 Ap 6 2 +-2 c -02/-01 1981 Mar 29 +-1 E -01/+00 2024 Mar 31 +-2 E -02/-01 +Z America/Sitka 14:58:47 - LMT 1867 O 19 15:30 +-9:1:13 - LMT 1900 Au 20 12 +-8 - PST 1942 +-8 u P%sT 1946 +-8 - PST 1969 +-8 u P%sT 1983 O 30 2 +-9 u Y%sT 1983 N 30 +-9 u AK%sT +Z America/St_Johns -3:30:52 - LMT 1884 +-3:30:52 j N%sT 1918 +-3:30:52 C N%sT 1919 +-3:30:52 j N%sT 1935 Mar 30 +-3:30 j N%sT 1942 May 11 +-3:30 C N%sT 1946 +-3:30 j N%sT 2011 N +-3:30 C N%sT +Z America/Swift_Current -7:11:20 - LMT 1905 S +-7 C M%sT 1946 Ap lastSu 2 +-7 r M%sT 1950 +-7 Sw M%sT 1972 Ap lastSu 2 +-6 - CST +Z America/Tegucigalpa -5:48:52 - LMT 1921 Ap +-6 HN C%sT +Z America/Thule -4:35:8 - LMT 1916 Jul 28 +-4 Th A%sT +Z America/Tijuana -7:48:4 - LMT 1922 Ja 1 7u +-7 - MST 1924 +-8 - PST 1927 Jun 10 23 +-7 - MST 1930 N 15 +-8 - PST 1931 Ap +-8 1 PDT 1931 S 30 +-8 - PST 1942 Ap 24 +-8 1 PWT 1945 Au 14 23u +-8 1 PPT 1945 N 12 +-8 - PST 1948 Ap 5 +-8 1 PDT 1949 Ja 14 +-8 - PST 1954 +-8 CA P%sT 1961 +-8 - PST 1976 +-8 u P%sT 1996 +-8 m P%sT 2001 +-8 u P%sT 2002 F 20 +-8 m P%sT 2010 +-8 u P%sT +Z America/Toronto -5:17:32 - LMT 1895 +-5 C E%sT 1919 +-5 t E%sT 1942 F 9 2s +-5 C E%sT 1946 +-5 t E%sT 1974 +-5 C E%sT +Z America/Vancouver -8:12:28 - LMT 1884 +-8 Va P%sT 1987 +-8 C P%sT +Z America/Whitehorse -9:0:12 - LMT 1900 Au 20 +-9 Y Y%sT 1965 +-9 Yu Y%sT 1966 F 27 +-8 - PST 1980 +-8 C P%sT 2020 N +-7 - MST +Z America/Winnipeg -6:28:36 - LMT 1887 Jul 16 +-6 W C%sT 2006 +-6 C C%sT +Z America/Yakutat 14:41:5 - LMT 1867 O 19 15:12:18 +-9:18:55 - LMT 1900 Au 20 12 +-9 - YST 1942 +-9 u Y%sT 1946 +-9 - YST 1969 +-9 u Y%sT 1983 N 30 +-9 u AK%sT +Z Antarctica/Casey 0 - -00 1969 +8 - +08 2009 O 18 2 +11 - +11 2010 Mar 5 2 +8 - +08 2011 O 28 2 +11 - +11 2012 F 21 17u +8 - +08 2016 O 22 +11 - +11 2018 Mar 11 4 +8 - +08 2018 O 7 4 +11 - +11 2019 Mar 17 3 +8 - +08 2019 O 4 3 +11 - +11 2020 Mar 8 3 +8 - +08 2020 O 4 0:1 +11 - +11 2021 Mar 14 +8 - +08 2021 O 3 0:1 +11 - +11 2022 Mar 13 +8 - +08 2022 O 2 0:1 +11 - +11 2023 Mar 9 3 +8 - +08 +Z Antarctica/Davis 0 - -00 1957 Ja 13 +7 - +07 1964 N +0 - -00 1969 F +7 - +07 2009 O 18 2 +5 - +05 2010 Mar 10 20u +7 - +07 2011 O 28 2 +5 - +05 2012 F 21 20u +7 - +07 +Z Antarctica/Macquarie 0 - -00 1899 N +10 - AEST 1916 O 1 2 +10 1 AEDT 1917 F +10 AU AE%sT 1919 Ap 1 0s +0 - -00 1948 Mar 25 +10 AU AE%sT 1967 +10 AT AE%sT 2010 +10 1 AEDT 2011 +10 AT AE%sT +Z Antarctica/Mawson 0 - -00 1954 F 13 +6 - +06 2009 O 18 2 +5 - +05 +Z Antarctica/Palmer 0 - -00 1965 +-4 A -04/-03 1969 O 5 +-3 A -03/-02 1982 May +-4 x -04/-03 2016 D 4 +-3 - -03 +Z Antarctica/Rothera 0 - -00 1976 D +-3 - -03 +Z Antarctica/Troll 0 - -00 2005 F 12 +0 Tr %s +Z Antarctica/Vostok 0 - -00 1957 D 16 +7 - +07 1994 F +0 - -00 1994 N +7 - +07 2023 D 18 2 +5 - +05 +Z Asia/Almaty 5:7:48 - LMT 1924 May 2 +5 - +05 1930 Jun 21 +6 R +06/+07 1991 Mar 31 2s +5 R +05/+06 1992 Ja 19 2s +6 R +06/+07 2004 O 31 2s +6 - +06 2024 Mar +5 - +05 +Z Asia/Amman 2:23:44 - LMT 1931 +2 J EE%sT 2022 O 28 0s +3 - +03 +Z Asia/Anadyr 11:49:56 - LMT 1924 May 2 +12 - +12 1930 Jun 21 +13 R +13/+14 1982 Ap 1 0s +12 R +12/+13 1991 Mar 31 2s +11 R +11/+12 1992 Ja 19 2s +12 R +12/+13 2010 Mar 28 2s +11 R +11/+12 2011 Mar 27 2s +12 - +12 +Z Asia/Aqtau 3:21:4 - LMT 1924 May 2 +4 - +04 1930 Jun 21 +5 - +05 1981 O +6 - +06 1982 Ap +5 R +05/+06 1991 Mar 31 2s +4 R +04/+05 1992 Ja 19 2s +5 R +05/+06 1994 S 25 2s +4 R +04/+05 2004 O 31 2s +5 - +05 +Z Asia/Aqtobe 3:48:40 - LMT 1924 May 2 +4 - +04 1930 Jun 21 +5 - +05 1981 Ap +5 1 +06 1981 O +6 - +06 1982 Ap +5 R +05/+06 1991 Mar 31 2s +4 R +04/+05 1992 Ja 19 2s +5 R +05/+06 2004 O 31 2s +5 - +05 +Z Asia/Ashgabat 3:53:32 - LMT 1924 May 2 +4 - +04 1930 Jun 21 +5 R +05/+06 1991 Mar 31 2 +4 R +04/+05 1992 Ja 19 2 +5 - +05 +Z Asia/Atyrau 3:27:44 - LMT 1924 May 2 +3 - +03 1930 Jun 21 +5 - +05 1981 O +6 - +06 1982 Ap +5 R +05/+06 1991 Mar 31 2s +4 R +04/+05 1992 Ja 19 2s +5 R +05/+06 1999 Mar 28 2s +4 R +04/+05 2004 O 31 2s +5 - +05 +Z Asia/Baghdad 2:57:40 - LMT 1890 +2:57:36 - BMT 1918 +3 - +03 1982 May +3 IQ +03/+04 +Z Asia/Baku 3:19:24 - LMT 1924 May 2 +3 - +03 1957 Mar +4 R +04/+05 1991 Mar 31 2s +3 R +03/+04 1992 S lastSu 2s +4 - +04 1996 +4 E +04/+05 1997 +4 AZ +04/+05 +Z Asia/Bangkok 6:42:4 - LMT 1880 +6:42:4 - BMT 1920 Ap +7 - +07 +Z Asia/Barnaul 5:35 - LMT 1919 D 10 +6 - +06 1930 Jun 21 +7 R +07/+08 1991 Mar 31 2s +6 R +06/+07 1992 Ja 19 2s +7 R +07/+08 1995 May 28 +6 R +06/+07 2011 Mar 27 2s +7 - +07 2014 O 26 2s +6 - +06 2016 Mar 27 2s +7 - +07 +Z Asia/Beirut 2:22 - LMT 1880 +2 l EE%sT +Z Asia/Bishkek 4:58:24 - LMT 1924 May 2 +5 - +05 1930 Jun 21 +6 R +06/+07 1991 Mar 31 2s +5 R +05/+06 1991 Au 31 2 +5 KG +05/+06 2005 Au 12 +6 - +06 +Z Asia/Chita 7:33:52 - LMT 1919 D 15 +8 - +08 1930 Jun 21 +9 R +09/+10 1991 Mar 31 2s +8 R +08/+09 1992 Ja 19 2s +9 R +09/+10 2011 Mar 27 2s +10 - +10 2014 O 26 2s +8 - +08 2016 Mar 27 2 +9 - +09 +Z Asia/Choibalsan 7:38 - LMT 1905 Au +7 - +07 1978 +8 - +08 1983 Ap +9 X +09/+10 2008 Mar 31 +8 X +08/+09 +Z Asia/Colombo 5:19:24 - LMT 1880 +5:19:32 - MMT 1906 +5:30 - +0530 1942 Ja 5 +5:30 0:30 +06 1942 S +5:30 1 +0630 1945 O 16 2 +5:30 - +0530 1996 May 25 +6:30 - +0630 1996 O 26 0:30 +6 - +06 2006 Ap 15 0:30 +5:30 - +0530 +Z Asia/Damascus 2:25:12 - LMT 1920 +2 S EE%sT 2022 O 28 +3 - +03 +Z Asia/Dhaka 6:1:40 - LMT 1890 +5:53:20 - HMT 1941 O +6:30 - +0630 1942 May 15 +5:30 - +0530 1942 S +6:30 - +0630 1951 S 30 +6 - +06 2009 +6 BD +06/+07 +Z Asia/Dili 8:22:20 - LMT 1912 +8 - +08 1942 F 21 23 +9 - +09 1976 May 3 +8 - +08 2000 S 17 +9 - +09 +Z Asia/Dubai 3:41:12 - LMT 1920 +4 - +04 +Z Asia/Dushanbe 4:35:12 - LMT 1924 May 2 +5 - +05 1930 Jun 21 +6 R +06/+07 1991 Mar 31 2s +5 1 +06 1991 S 9 2s +5 - +05 +Z Asia/Famagusta 2:15:48 - LMT 1921 N 14 +2 CY EE%sT 1998 S +2 E EE%sT 2016 S 8 +3 - +03 2017 O 29 1u +2 E EE%sT +Z Asia/Gaza 2:17:52 - LMT 1900 O +2 Z EET/EEST 1948 May 15 +2 K EE%sT 1967 Jun 5 +2 Z I%sT 1996 +2 J EE%sT 1999 +2 P EE%sT 2008 Au 29 +2 - EET 2008 S +2 P EE%sT 2010 +2 - EET 2010 Mar 27 0:1 +2 P EE%sT 2011 Au +2 - EET 2012 +2 P EE%sT +Z Asia/Hebron 2:20:23 - LMT 1900 O +2 Z EET/EEST 1948 May 15 +2 K EE%sT 1967 Jun 5 +2 Z I%sT 1996 +2 J EE%sT 1999 +2 P EE%sT +Z Asia/Ho_Chi_Minh 7:6:30 - LMT 1906 Jul +7:6:30 - PLMT 1911 May +7 - +07 1942 D 31 23 +8 - +08 1945 Mar 14 23 +9 - +09 1945 S 1 24 +7 - +07 1947 Ap +8 - +08 1955 Jul 1 1 +7 - +07 1959 D 31 23 +8 - +08 1975 Jun 13 +7 - +07 +Z Asia/Hong_Kong 7:36:42 - LMT 1904 O 29 17u +8 - HKT 1941 Jun 15 3 +8 1 HKST 1941 O 1 4 +8 0:30 HKWT 1941 D 25 +9 - JST 1945 N 18 2 +8 HK HK%sT +Z Asia/Hovd 6:6:36 - LMT 1905 Au +6 - +06 1978 +7 X +07/+08 +Z Asia/Irkutsk 6:57:5 - LMT 1880 +6:57:5 - IMT 1920 Ja 25 +7 - +07 1930 Jun 21 +8 R +08/+09 1991 Mar 31 2s +7 R +07/+08 1992 Ja 19 2s +8 R +08/+09 2011 Mar 27 2s +9 - +09 2014 O 26 2s +8 - +08 +Z Asia/Jakarta 7:7:12 - LMT 1867 Au 10 +7:7:12 - BMT 1923 D 31 16:40u +7:20 - +0720 1932 N +7:30 - +0730 1942 Mar 23 +9 - +09 1945 S 23 +7:30 - +0730 1948 May +8 - +08 1950 May +7:30 - +0730 1964 +7 - WIB +Z Asia/Jayapura 9:22:48 - LMT 1932 N +9 - +09 1944 S +9:30 - +0930 1964 +9 - WIT +Z Asia/Jerusalem 2:20:54 - LMT 1880 +2:20:40 - JMT 1918 +2 Z I%sT +Z Asia/Kabul 4:36:48 - LMT 1890 +4 - +04 1945 +4:30 - +0430 +Z Asia/Kamchatka 10:34:36 - LMT 1922 N 10 +11 - +11 1930 Jun 21 +12 R +12/+13 1991 Mar 31 2s +11 R +11/+12 1992 Ja 19 2s +12 R +12/+13 2010 Mar 28 2s +11 R +11/+12 2011 Mar 27 2s +12 - +12 +Z Asia/Karachi 4:28:12 - LMT 1907 +5:30 - +0530 1942 S +5:30 1 +0630 1945 O 15 +5:30 - +0530 1951 S 30 +5 - +05 1971 Mar 26 +5 PK PK%sT +Z Asia/Kathmandu 5:41:16 - LMT 1920 +5:30 - +0530 1986 +5:45 - +0545 +Z Asia/Khandyga 9:2:13 - LMT 1919 D 15 +8 - +08 1930 Jun 21 +9 R +09/+10 1991 Mar 31 2s +8 R +08/+09 1992 Ja 19 2s +9 R +09/+10 2004 +10 R +10/+11 2011 Mar 27 2s +11 - +11 2011 S 13 0s +10 - +10 2014 O 26 2s +9 - +09 +Z Asia/Kolkata 5:53:28 - LMT 1854 Jun 28 +5:53:20 - HMT 1870 +5:21:10 - MMT 1906 +5:30 - IST 1941 O +5:30 1 +0630 1942 May 15 +5:30 - IST 1942 S +5:30 1 +0630 1945 O 15 +5:30 - IST +Z Asia/Krasnoyarsk 6:11:26 - LMT 1920 Ja 6 +6 - +06 1930 Jun 21 +7 R +07/+08 1991 Mar 31 2s +6 R +06/+07 1992 Ja 19 2s +7 R +07/+08 2011 Mar 27 2s +8 - +08 2014 O 26 2s +7 - +07 +Z Asia/Kuching 7:21:20 - LMT 1926 Mar +7:30 - +0730 1933 +8 NB +08/+0820 1942 F 16 +9 - +09 1945 S 12 +8 - +08 +Z Asia/Macau 7:34:10 - LMT 1904 O 30 +8 - CST 1941 D 21 23 +9 _ +09/+10 1945 S 30 24 +8 _ C%sT +Z Asia/Magadan 10:3:12 - LMT 1924 May 2 +10 - +10 1930 Jun 21 +11 R +11/+12 1991 Mar 31 2s +10 R +10/+11 1992 Ja 19 2s +11 R +11/+12 2011 Mar 27 2s +12 - +12 2014 O 26 2s +10 - +10 2016 Ap 24 2s +11 - +11 +Z Asia/Makassar 7:57:36 - LMT 1920 +7:57:36 - MMT 1932 N +8 - +08 1942 F 9 +9 - +09 1945 S 23 +8 - WITA +Z Asia/Manila -15:56 - LMT 1844 D 31 +8:4 - LMT 1899 May 11 +8 PH P%sT 1942 May +9 - JST 1944 N +8 PH P%sT +Z Asia/Nicosia 2:13:28 - LMT 1921 N 14 +2 CY EE%sT 1998 S +2 E EE%sT +Z Asia/Novokuznetsk 5:48:48 - LMT 1924 May +6 - +06 1930 Jun 21 +7 R +07/+08 1991 Mar 31 2s +6 R +06/+07 1992 Ja 19 2s +7 R +07/+08 2010 Mar 28 2s +6 R +06/+07 2011 Mar 27 2s +7 - +07 +Z Asia/Novosibirsk 5:31:40 - LMT 1919 D 14 6 +6 - +06 1930 Jun 21 +7 R +07/+08 1991 Mar 31 2s +6 R +06/+07 1992 Ja 19 2s +7 R +07/+08 1993 May 23 +6 R +06/+07 2011 Mar 27 2s +7 - +07 2014 O 26 2s +6 - +06 2016 Jul 24 2s +7 - +07 +Z Asia/Omsk 4:53:30 - LMT 1919 N 14 +5 - +05 1930 Jun 21 +6 R +06/+07 1991 Mar 31 2s +5 R +05/+06 1992 Ja 19 2s +6 R +06/+07 2011 Mar 27 2s +7 - +07 2014 O 26 2s +6 - +06 +Z Asia/Oral 3:25:24 - LMT 1924 May 2 +3 - +03 1930 Jun 21 +5 - +05 1981 Ap +5 1 +06 1981 O +6 - +06 1982 Ap +5 R +05/+06 1989 Mar 26 2s +4 R +04/+05 1992 Ja 19 2s +5 R +05/+06 1992 Mar 29 2s +4 R +04/+05 2004 O 31 2s +5 - +05 +Z Asia/Pontianak 7:17:20 - LMT 1908 May +7:17:20 - PMT 1932 N +7:30 - +0730 1942 Ja 29 +9 - +09 1945 S 23 +7:30 - +0730 1948 May +8 - +08 1950 May +7:30 - +0730 1964 +8 - WITA 1988 +7 - WIB +Z Asia/Pyongyang 8:23 - LMT 1908 Ap +8:30 - KST 1912 +9 - JST 1945 Au 24 +9 - KST 2015 Au 15 +8:30 - KST 2018 May 4 23:30 +9 - KST +Z Asia/Qatar 3:26:8 - LMT 1920 +4 - +04 1972 Jun +3 - +03 +Z Asia/Qostanay 4:14:28 - LMT 1924 May 2 +4 - +04 1930 Jun 21 +5 - +05 1981 Ap +5 1 +06 1981 O +6 - +06 1982 Ap +5 R +05/+06 1991 Mar 31 2s +4 R +04/+05 1992 Ja 19 2s +5 R +05/+06 2004 O 31 2s +6 - +06 2024 Mar +5 - +05 +Z Asia/Qyzylorda 4:21:52 - LMT 1924 May 2 +4 - +04 1930 Jun 21 +5 - +05 1981 Ap +5 1 +06 1981 O +6 - +06 1982 Ap +5 R +05/+06 1991 Mar 31 2s +4 R +04/+05 1991 S 29 2s +5 R +05/+06 1992 Ja 19 2s +6 R +06/+07 1992 Mar 29 2s +5 R +05/+06 2004 O 31 2s +6 - +06 2018 D 21 +5 - +05 +Z Asia/Riyadh 3:6:52 - LMT 1947 Mar 14 +3 - +03 +Z Asia/Sakhalin 9:30:48 - LMT 1905 Au 23 +9 - +09 1945 Au 25 +11 R +11/+12 1991 Mar 31 2s +10 R +10/+11 1992 Ja 19 2s +11 R +11/+12 1997 Mar lastSu 2s +10 R +10/+11 2011 Mar 27 2s +11 - +11 2014 O 26 2s +10 - +10 2016 Mar 27 2s +11 - +11 +Z Asia/Samarkand 4:27:53 - LMT 1924 May 2 +4 - +04 1930 Jun 21 +5 - +05 1981 Ap +5 1 +06 1981 O +6 - +06 1982 Ap +5 R +05/+06 1992 +5 - +05 +Z Asia/Seoul 8:27:52 - LMT 1908 Ap +8:30 - KST 1912 +9 - JST 1945 S 8 +9 KR K%sT 1954 Mar 21 +8:30 KR K%sT 1961 Au 10 +9 KR K%sT +Z Asia/Shanghai 8:5:43 - LMT 1901 +8 Sh C%sT 1949 May 28 +8 CN C%sT +Z Asia/Singapore 6:55:25 - LMT 1901 +6:55:25 - SMT 1905 Jun +7 - +07 1933 +7 0:20 +0720 1936 +7:20 - +0720 1941 S +7:30 - +0730 1942 F 16 +9 - +09 1945 S 12 +7:30 - +0730 1981 D 31 16u +8 - +08 +Z Asia/Srednekolymsk 10:14:52 - LMT 1924 May 2 +10 - +10 1930 Jun 21 +11 R +11/+12 1991 Mar 31 2s +10 R +10/+11 1992 Ja 19 2s +11 R +11/+12 2011 Mar 27 2s +12 - +12 2014 O 26 2s +11 - +11 +Z Asia/Taipei 8:6 - LMT 1896 +8 - CST 1937 O +9 - JST 1945 S 21 1 +8 f C%sT +Z Asia/Tashkent 4:37:11 - LMT 1924 May 2 +5 - +05 1930 Jun 21 +6 R +06/+07 1991 Mar 31 2 +5 R +05/+06 1992 +5 - +05 +Z Asia/Tbilisi 2:59:11 - LMT 1880 +2:59:11 - TBMT 1924 May 2 +3 - +03 1957 Mar +4 R +04/+05 1991 Mar 31 2s +3 R +03/+04 1992 +3 e +03/+04 1994 S lastSu +4 e +04/+05 1996 O lastSu +4 1 +05 1997 Mar lastSu +4 e +04/+05 2004 Jun 27 +3 R +03/+04 2005 Mar lastSu 2 +4 - +04 +Z Asia/Tehran 3:25:44 - LMT 1916 +3:25:44 - TMT 1935 Jun 13 +3:30 i +0330/+0430 1977 O 20 24 +4 i +04/+05 1979 +3:30 i +0330/+0430 +Z Asia/Thimphu 5:58:36 - LMT 1947 Au 15 +5:30 - +0530 1987 O +6 - +06 +Z Asia/Tokyo 9:18:59 - LMT 1887 D 31 15u +9 JP J%sT +Z Asia/Tomsk 5:39:51 - LMT 1919 D 22 +6 - +06 1930 Jun 21 +7 R +07/+08 1991 Mar 31 2s +6 R +06/+07 1992 Ja 19 2s +7 R +07/+08 2002 May 1 3 +6 R +06/+07 2011 Mar 27 2s +7 - +07 2014 O 26 2s +6 - +06 2016 May 29 2s +7 - +07 +Z Asia/Ulaanbaatar 7:7:32 - LMT 1905 Au +7 - +07 1978 +8 X +08/+09 +Z Asia/Urumqi 5:50:20 - LMT 1928 +6 - +06 +Z Asia/Ust-Nera 9:32:54 - LMT 1919 D 15 +8 - +08 1930 Jun 21 +9 R +09/+10 1981 Ap +11 R +11/+12 1991 Mar 31 2s +10 R +10/+11 1992 Ja 19 2s +11 R +11/+12 2011 Mar 27 2s +12 - +12 2011 S 13 0s +11 - +11 2014 O 26 2s +10 - +10 +Z Asia/Vladivostok 8:47:31 - LMT 1922 N 15 +9 - +09 1930 Jun 21 +10 R +10/+11 1991 Mar 31 2s +9 R +09/+10 1992 Ja 19 2s +10 R +10/+11 2011 Mar 27 2s +11 - +11 2014 O 26 2s +10 - +10 +Z Asia/Yakutsk 8:38:58 - LMT 1919 D 15 +8 - +08 1930 Jun 21 +9 R +09/+10 1991 Mar 31 2s +8 R +08/+09 1992 Ja 19 2s +9 R +09/+10 2011 Mar 27 2s +10 - +10 2014 O 26 2s +9 - +09 +Z Asia/Yangon 6:24:47 - LMT 1880 +6:24:47 - RMT 1920 +6:30 - +0630 1942 May +9 - +09 1945 May 3 +6:30 - +0630 +Z Asia/Yekaterinburg 4:2:33 - LMT 1916 Jul 3 +3:45:5 - PMT 1919 Jul 15 4 +4 - +04 1930 Jun 21 +5 R +05/+06 1991 Mar 31 2s +4 R +04/+05 1992 Ja 19 2s +5 R +05/+06 2011 Mar 27 2s +6 - +06 2014 O 26 2s +5 - +05 +Z Asia/Yerevan 2:58 - LMT 1924 May 2 +3 - +03 1957 Mar +4 R +04/+05 1991 Mar 31 2s +3 R +03/+04 1995 S 24 2s +4 - +04 1997 +4 R +04/+05 2011 +4 AM +04/+05 +Z Atlantic/Azores -1:42:40 - LMT 1884 +-1:54:32 - HMT 1912 Ja 1 2u +-2 p -02/-01 1942 Ap 25 22s +-2 p +00 1942 Au 15 22s +-2 p -02/-01 1943 Ap 17 22s +-2 p +00 1943 Au 28 22s +-2 p -02/-01 1944 Ap 22 22s +-2 p +00 1944 Au 26 22s +-2 p -02/-01 1945 Ap 21 22s +-2 p +00 1945 Au 25 22s +-2 p -02/-01 1966 Ap 3 2 +-1 p -01/+00 1983 S 25 1s +-1 W- -01/+00 1992 S 27 1s +0 E WE%sT 1993 Mar 28 1u +-1 E -01/+00 +Z Atlantic/Bermuda -4:19:18 - LMT 1890 +-4:19:18 Be BMT/BST 1930 Ja 1 2 +-4 Be A%sT 1974 Ap 28 2 +-4 C A%sT 1976 +-4 u A%sT +Z Atlantic/Canary -1:1:36 - LMT 1922 Mar +-1 - -01 1946 S 30 1 +0 - WET 1980 Ap 6 0s +0 1 WEST 1980 S 28 1u +0 E WE%sT +Z Atlantic/Cape_Verde -1:34:4 - LMT 1912 Ja 1 2u +-2 - -02 1942 S +-2 1 -01 1945 O 15 +-2 - -02 1975 N 25 2 +-1 - -01 +Z Atlantic/Faroe -0:27:4 - LMT 1908 Ja 11 +0 - WET 1981 +0 E WE%sT +Z Atlantic/Madeira -1:7:36 - LMT 1884 +-1:7:36 - FMT 1912 Ja 1 1u +-1 p -01/+00 1942 Ap 25 22s +-1 p +01 1942 Au 15 22s +-1 p -01/+00 1943 Ap 17 22s +-1 p +01 1943 Au 28 22s +-1 p -01/+00 1944 Ap 22 22s +-1 p +01 1944 Au 26 22s +-1 p -01/+00 1945 Ap 21 22s +-1 p +01 1945 Au 25 22s +-1 p -01/+00 1966 Ap 3 2 +0 p WE%sT 1983 S 25 1s +0 E WE%sT +Z Atlantic/South_Georgia -2:26:8 - LMT 1890 +-2 - -02 +Z Atlantic/Stanley -3:51:24 - LMT 1890 +-3:51:24 - SMT 1912 Mar 12 +-4 FK -04/-03 1983 May +-3 FK -03/-02 1985 S 15 +-4 FK -04/-03 2010 S 5 2 +-3 - -03 +Z Australia/Adelaide 9:14:20 - LMT 1895 F +9 - ACST 1899 May +9:30 AU AC%sT 1971 +9:30 AS AC%sT +Z Australia/Brisbane 10:12:8 - LMT 1895 +10 AU AE%sT 1971 +10 AQ AE%sT +Z Australia/Broken_Hill 9:25:48 - LMT 1895 F +10 - AEST 1896 Au 23 +9 - ACST 1899 May +9:30 AU AC%sT 1971 +9:30 AN AC%sT 2000 +9:30 AS AC%sT +Z Australia/Darwin 8:43:20 - LMT 1895 F +9 - ACST 1899 May +9:30 AU AC%sT +Z Australia/Eucla 8:35:28 - LMT 1895 D +8:45 AU +0845/+0945 1943 Jul +8:45 AW +0845/+0945 +Z Australia/Hobart 9:49:16 - LMT 1895 S +10 AT AE%sT 1919 O 24 +10 AU AE%sT 1967 +10 AT AE%sT +Z Australia/Lindeman 9:55:56 - LMT 1895 +10 AU AE%sT 1971 +10 AQ AE%sT 1992 Jul +10 Ho AE%sT +Z Australia/Lord_Howe 10:36:20 - LMT 1895 F +10 - AEST 1981 Mar +10:30 LH +1030/+1130 1985 Jul +10:30 LH +1030/+11 +Z Australia/Melbourne 9:39:52 - LMT 1895 F +10 AU AE%sT 1971 +10 AV AE%sT +Z Australia/Perth 7:43:24 - LMT 1895 D +8 AU AW%sT 1943 Jul +8 AW AW%sT +Z Australia/Sydney 10:4:52 - LMT 1895 F +10 AU AE%sT 1971 +10 AN AE%sT +Z CET 1 c CE%sT +Z CST6CDT -6 u C%sT +Z EET 2 E EE%sT +Z EST -5 - EST +Z EST5EDT -5 u E%sT Z Etc/GMT 0 - GMT -L Etc/GMT GMT -Z Etc/GMT-14 14 - +14 -Z Etc/GMT-13 13 - +13 -Z Etc/GMT-12 12 - +12 -Z Etc/GMT-11 11 - +11 -Z Etc/GMT-10 10 - +10 -Z Etc/GMT-9 9 - +09 -Z Etc/GMT-8 8 - +08 -Z Etc/GMT-7 7 - +07 -Z Etc/GMT-6 6 - +06 -Z Etc/GMT-5 5 - +05 -Z Etc/GMT-4 4 - +04 -Z Etc/GMT-3 3 - +03 -Z Etc/GMT-2 2 - +02 -Z Etc/GMT-1 1 - +01 Z Etc/GMT+1 -1 - -01 +Z Etc/GMT+10 -10 - -10 +Z Etc/GMT+11 -11 - -11 +Z Etc/GMT+12 -12 - -12 Z Etc/GMT+2 -2 - -02 Z Etc/GMT+3 -3 - -03 Z Etc/GMT+4 -4 - -04 @@ -4034,10 +3591,463 @@ Z Etc/GMT+7 -7 - -07 Z Etc/GMT+8 -8 - -08 Z Etc/GMT+9 -9 - -09 -Z Etc/GMT+10 -10 - -10 -Z Etc/GMT+11 -11 - -11 -Z Etc/GMT+12 -12 - -12 +Z Etc/GMT-1 1 - +01 +Z Etc/GMT-10 10 - +10 +Z Etc/GMT-11 11 - +11 +Z Etc/GMT-12 12 - +12 +Z Etc/GMT-13 13 - +13 +Z Etc/GMT-14 14 - +14 +Z Etc/GMT-2 2 - +02 +Z Etc/GMT-3 3 - +03 +Z Etc/GMT-4 4 - +04 +Z Etc/GMT-5 5 - +05 +Z Etc/GMT-6 6 - +06 +Z Etc/GMT-7 7 - +07 +Z Etc/GMT-8 8 - +08 +Z Etc/GMT-9 9 - +09 +Z Etc/UTC 0 - UTC +Z Europe/Andorra 0:6:4 - LMT 1901 +0 - WET 1946 S 30 +1 - CET 1985 Mar 31 2 +1 E CE%sT +Z Europe/Astrakhan 3:12:12 - LMT 1924 May +3 - +03 1930 Jun 21 +4 R +04/+05 1989 Mar 26 2s +3 R +03/+04 1991 Mar 31 2s +4 - +04 1992 Mar 29 2s +3 R +03/+04 2011 Mar 27 2s +4 - +04 2014 O 26 2s +3 - +03 2016 Mar 27 2s +4 - +04 +Z Europe/Athens 1:34:52 - LMT 1895 S 14 +1:34:52 - AMT 1916 Jul 28 0:1 +2 g EE%sT 1941 Ap 30 +1 g CE%sT 1944 Ap 4 +2 g EE%sT 1981 +2 E EE%sT +Z Europe/Belgrade 1:22 - LMT 1884 +1 - CET 1941 Ap 18 23 +1 c CE%sT 1945 +1 - CET 1945 May 8 2s +1 1 CEST 1945 S 16 2s +1 - CET 1982 N 27 +1 E CE%sT +Z Europe/Berlin 0:53:28 - LMT 1893 Ap +1 c CE%sT 1945 May 24 2 +1 So CE%sT 1946 +1 DE CE%sT 1980 +1 E CE%sT +Z Europe/Brussels 0:17:30 - LMT 1880 +0:17:30 - BMT 1892 May 1 0:17:30 +0 - WET 1914 N 8 +1 - CET 1916 May +1 c CE%sT 1918 N 11 11u +0 b WE%sT 1940 May 20 2s +1 c CE%sT 1944 S 3 +1 b CE%sT 1977 +1 E CE%sT +Z Europe/Bucharest 1:44:24 - LMT 1891 O +1:44:24 - BMT 1931 Jul 24 +2 z EE%sT 1981 Mar 29 2s +2 c EE%sT 1991 +2 z EE%sT 1994 +2 e EE%sT 1997 +2 E EE%sT +Z Europe/Budapest 1:16:20 - LMT 1890 N +1 c CE%sT 1918 +1 h CE%sT 1941 Ap 7 23 +1 c CE%sT 1945 +1 h CE%sT 1984 +1 E CE%sT +Z Europe/Chisinau 1:55:20 - LMT 1880 +1:55 - CMT 1918 F 15 +1:44:24 - BMT 1931 Jul 24 +2 z EE%sT 1940 Au 15 +2 1 EEST 1941 Jul 17 +1 c CE%sT 1944 Au 24 +3 R MSK/MSD 1990 May 6 2 +2 R EE%sT 1992 +2 e EE%sT 1997 +2 MD EE%sT +Z Europe/Dublin -0:25:21 - LMT 1880 Au 2 +-0:25:21 - DMT 1916 May 21 2s +-0:25:21 1 IST 1916 O 1 2s +0 G %s 1921 D 6 +0 G GMT/IST 1940 F 25 2s +0 1 IST 1946 O 6 2s +0 - GMT 1947 Mar 16 2s +0 1 IST 1947 N 2 2s +0 - GMT 1948 Ap 18 2s +0 G GMT/IST 1968 O 27 +1 IE IST/GMT +Z Europe/Gibraltar -0:21:24 - LMT 1880 Au 2 +0 G %s 1957 Ap 14 2 +1 - CET 1982 +1 E CE%sT +Z Europe/Helsinki 1:39:49 - LMT 1878 May 31 +1:39:49 - HMT 1921 May +2 FI EE%sT 1983 +2 E EE%sT +Z Europe/Istanbul 1:55:52 - LMT 1880 +1:56:56 - IMT 1910 O +2 T EE%sT 1978 Jun 29 +3 T +03/+04 1984 N 1 2 +2 T EE%sT 2007 +2 E EE%sT 2011 Mar 27 1u +2 - EET 2011 Mar 28 1u +2 E EE%sT 2014 Mar 30 1u +2 - EET 2014 Mar 31 1u +2 E EE%sT 2015 O 25 1u +2 1 EEST 2015 N 8 1u +2 E EE%sT 2016 S 7 +3 - +03 +Z Europe/Kaliningrad 1:22 - LMT 1893 Ap +1 c CE%sT 1945 Ap 10 +2 O EE%sT 1946 Ap 7 +3 R MSK/MSD 1989 Mar 26 2s +2 R EE%sT 2011 Mar 27 2s +3 - +03 2014 O 26 2s +2 - EET +Z Europe/Kirov 3:18:48 - LMT 1919 Jul 1 0u +3 - +03 1930 Jun 21 +4 R +04/+05 1989 Mar 26 2s +3 R MSK/MSD 1991 Mar 31 2s +4 - +04 1992 Mar 29 2s +3 R MSK/MSD 2011 Mar 27 2s +4 - MSK 2014 O 26 2s +3 - MSK +Z Europe/Kyiv 2:2:4 - LMT 1880 +2:2:4 - KMT 1924 May 2 +2 - EET 1930 Jun 21 +3 - MSK 1941 S 20 +1 c CE%sT 1943 N 6 +3 R MSK/MSD 1990 Jul 1 2 +2 1 EEST 1991 S 29 3 +2 c EE%sT 1996 May 13 +2 E EE%sT +Z Europe/Lisbon -0:36:45 - LMT 1884 +-0:36:45 - LMT 1912 Ja 1 0u +0 p WE%sT 1966 Ap 3 2 +1 - CET 1976 S 26 1 +0 p WE%sT 1983 S 25 1s +0 W- WE%sT 1992 S 27 1s +1 E CE%sT 1996 Mar 31 1u +0 E WE%sT +Z Europe/London -0:1:15 - LMT 1847 D +0 G %s 1968 O 27 +1 - BST 1971 O 31 2u +0 G %s 1996 +0 E GMT/BST +Z Europe/Madrid -0:14:44 - LMT 1901 Ja 1 0u +0 s WE%sT 1940 Mar 16 23 +1 s CE%sT 1979 +1 E CE%sT +Z Europe/Malta 0:58:4 - LMT 1893 N 2 +1 I CE%sT 1973 Mar 31 +1 MT CE%sT 1981 +1 E CE%sT +Z Europe/Minsk 1:50:16 - LMT 1880 +1:50 - MMT 1924 May 2 +2 - EET 1930 Jun 21 +3 - MSK 1941 Jun 28 +1 c CE%sT 1944 Jul 3 +3 R MSK/MSD 1990 +3 - MSK 1991 Mar 31 2s +2 R EE%sT 2011 Mar 27 2s +3 - +03 +Z Europe/Moscow 2:30:17 - LMT 1880 +2:30:17 - MMT 1916 Jul 3 +2:31:19 R %s 1919 Jul 1 0u +3 R %s 1921 O +3 R MSK/MSD 1922 O +2 - EET 1930 Jun 21 +3 R MSK/MSD 1991 Mar 31 2s +2 R EE%sT 1992 Ja 19 2s +3 R MSK/MSD 2011 Mar 27 2s +4 - MSK 2014 O 26 2s +3 - MSK +Z Europe/Paris 0:9:21 - LMT 1891 Mar 16 +0:9:21 - PMT 1911 Mar 11 +0 F WE%sT 1940 Jun 14 23 +1 c CE%sT 1944 Au 25 +0 F WE%sT 1945 S 16 3 +1 F CE%sT 1977 +1 E CE%sT +Z Europe/Prague 0:57:44 - LMT 1850 +0:57:44 - PMT 1891 O +1 c CE%sT 1945 May 9 +1 CZ CE%sT 1946 D 1 3 +1 -1 GMT 1947 F 23 2 +1 CZ CE%sT 1979 +1 E CE%sT +Z Europe/Riga 1:36:34 - LMT 1880 +1:36:34 - RMT 1918 Ap 15 2 +1:36:34 1 LST 1918 S 16 3 +1:36:34 - RMT 1919 Ap 1 2 +1:36:34 1 LST 1919 May 22 3 +1:36:34 - RMT 1926 May 11 +2 - EET 1940 Au 5 +3 - MSK 1941 Jul +1 c CE%sT 1944 O 13 +3 R MSK/MSD 1989 Mar lastSu 2s +2 1 EEST 1989 S lastSu 2s +2 LV EE%sT 1997 Ja 21 +2 E EE%sT 2000 F 29 +2 - EET 2001 Ja 2 +2 E EE%sT +Z Europe/Rome 0:49:56 - LMT 1866 D 12 +0:49:56 - RMT 1893 O 31 23u +1 I CE%sT 1943 S 10 +1 c CE%sT 1944 Jun 4 +1 I CE%sT 1980 +1 E CE%sT +Z Europe/Samara 3:20:20 - LMT 1919 Jul 1 0u +3 - +03 1930 Jun 21 +4 - +04 1935 Ja 27 +4 R +04/+05 1989 Mar 26 2s +3 R +03/+04 1991 Mar 31 2s +2 R +02/+03 1991 S 29 2s +3 - +03 1991 O 20 3 +4 R +04/+05 2010 Mar 28 2s +3 R +03/+04 2011 Mar 27 2s +4 - +04 +Z Europe/Saratov 3:4:18 - LMT 1919 Jul 1 0u +3 - +03 1930 Jun 21 +4 R +04/+05 1988 Mar 27 2s +3 R +03/+04 1991 Mar 31 2s +4 - +04 1992 Mar 29 2s +3 R +03/+04 2011 Mar 27 2s +4 - +04 2014 O 26 2s +3 - +03 2016 D 4 2s +4 - +04 +Z Europe/Simferopol 2:16:24 - LMT 1880 +2:16 - SMT 1924 May 2 +2 - EET 1930 Jun 21 +3 - MSK 1941 N +1 c CE%sT 1944 Ap 13 +3 R MSK/MSD 1990 +3 - MSK 1990 Jul 1 2 +2 - EET 1992 Mar 20 +2 c EE%sT 1994 May +3 c MSK/MSD 1996 Mar 31 0s +3 1 MSD 1996 O 27 3s +3 - MSK 1997 Mar lastSu 1u +2 E EE%sT 2014 Mar 30 2 +4 - MSK 2014 O 26 2s +3 - MSK +Z Europe/Sofia 1:33:16 - LMT 1880 +1:56:56 - IMT 1894 N 30 +2 - EET 1942 N 2 3 +1 c CE%sT 1945 +1 - CET 1945 Ap 2 3 +2 - EET 1979 Mar 31 23 +2 BG EE%sT 1982 S 26 3 +2 c EE%sT 1991 +2 e EE%sT 1997 +2 E EE%sT +Z Europe/Tallinn 1:39 - LMT 1880 +1:39 - TMT 1918 F +1 c CE%sT 1919 Jul +1:39 - TMT 1921 May +2 - EET 1940 Au 6 +3 - MSK 1941 S 15 +1 c CE%sT 1944 S 22 +3 R MSK/MSD 1989 Mar 26 2s +2 1 EEST 1989 S 24 2s +2 c EE%sT 1998 S 22 +2 E EE%sT 1999 O 31 4 +2 - EET 2002 F 21 +2 E EE%sT +Z Europe/Tirane 1:19:20 - LMT 1914 +1 - CET 1940 Jun 16 +1 q CE%sT 1984 Jul +1 E CE%sT +Z Europe/Ulyanovsk 3:13:36 - LMT 1919 Jul 1 0u +3 - +03 1930 Jun 21 +4 R +04/+05 1989 Mar 26 2s +3 R +03/+04 1991 Mar 31 2s +2 R +02/+03 1992 Ja 19 2s +3 R +03/+04 2011 Mar 27 2s +4 - +04 2014 O 26 2s +3 - +03 2016 Mar 27 2s +4 - +04 +Z Europe/Vienna 1:5:21 - LMT 1893 Ap +1 c CE%sT 1920 +1 a CE%sT 1940 Ap 1 2s +1 c CE%sT 1945 Ap 2 2s +1 1 CEST 1945 Ap 12 2s +1 - CET 1946 +1 a CE%sT 1981 +1 E CE%sT +Z Europe/Vilnius 1:41:16 - LMT 1880 +1:24 - WMT 1917 +1:35:36 - KMT 1919 O 10 +1 - CET 1920 Jul 12 +2 - EET 1920 O 9 +1 - CET 1940 Au 3 +3 - MSK 1941 Jun 24 +1 c CE%sT 1944 Au +3 R MSK/MSD 1989 Mar 26 2s +2 R EE%sT 1991 S 29 2s +2 c EE%sT 1998 +2 - EET 1998 Mar 29 1u +1 E CE%sT 1999 O 31 1u +2 - EET 2003 +2 E EE%sT +Z Europe/Volgograd 2:57:40 - LMT 1920 Ja 3 +3 - +03 1930 Jun 21 +4 - +04 1961 N 11 +4 R +04/+05 1988 Mar 27 2s +3 R MSK/MSD 1991 Mar 31 2s +4 - +04 1992 Mar 29 2s +3 R MSK/MSD 2011 Mar 27 2s +4 - MSK 2014 O 26 2s +3 - MSK 2018 O 28 2s +4 - +04 2020 D 27 2s +3 - MSK +Z Europe/Warsaw 1:24 - LMT 1880 +1:24 - WMT 1915 Au 5 +1 c CE%sT 1918 S 16 3 +2 O EE%sT 1922 Jun +1 O CE%sT 1940 Jun 23 2 +1 c CE%sT 1944 O +1 O CE%sT 1977 +1 W- CE%sT 1988 +1 E CE%sT +Z Europe/Zurich 0:34:8 - LMT 1853 Jul 16 +0:29:46 - BMT 1894 Jun +1 CH CE%sT 1981 +1 E CE%sT Z Factory 0 - -00 +Z HST -10 - HST +Z Indian/Chagos 4:49:40 - LMT 1907 +5 - +05 1996 +6 - +06 +Z Indian/Maldives 4:54 - LMT 1880 +4:54 - MMT 1960 +5 - +05 +Z Indian/Mauritius 3:50 - LMT 1907 +4 MU +04/+05 +Z MET 1 c ME%sT +Z MST -7 - MST +Z MST7MDT -7 u M%sT +Z PST8PDT -8 u P%sT +Z Pacific/Apia 12:33:4 - LMT 1892 Jul 5 +-11:26:56 - LMT 1911 +-11:30 - -1130 1950 +-11 WS -11/-10 2011 D 29 24 +13 WS +13/+14 +Z Pacific/Auckland 11:39:4 - LMT 1868 N 2 +11:30 NZ NZ%sT 1946 +12 NZ NZ%sT +Z Pacific/Bougainville 10:22:16 - LMT 1880 +9:48:32 - PMMT 1895 +10 - +10 1942 Jul +9 - +09 1945 Au 21 +10 - +10 2014 D 28 2 +11 - +11 +Z Pacific/Chatham 12:13:48 - LMT 1868 N 2 +12:15 - +1215 1946 +12:45 k +1245/+1345 +Z Pacific/Easter -7:17:28 - LMT 1890 +-7:17:28 - EMT 1932 S +-7 x -07/-06 1982 Mar 14 3u +-6 x -06/-05 +Z Pacific/Efate 11:13:16 - LMT 1912 Ja 13 +11 VU +11/+12 +Z Pacific/Fakaofo -11:24:56 - LMT 1901 +-11 - -11 2011 D 30 +13 - +13 +Z Pacific/Fiji 11:55:44 - LMT 1915 O 26 +12 FJ +12/+13 +Z Pacific/Galapagos -5:58:24 - LMT 1931 +-5 - -05 1986 +-6 EC -06/-05 +Z Pacific/Gambier -8:59:48 - LMT 1912 O +-9 - -09 +Z Pacific/Guadalcanal 10:39:48 - LMT 1912 O +11 - +11 +Z Pacific/Guam -14:21 - LMT 1844 D 31 +9:39 - LMT 1901 +10 - GST 1941 D 10 +9 - +09 1944 Jul 31 +10 Gu G%sT 2000 D 23 +10 - ChST +Z Pacific/Honolulu -10:31:26 - LMT 1896 Ja 13 12 +-10:30 - HST 1933 Ap 30 2 +-10:30 1 HDT 1933 May 21 12 +-10:30 u H%sT 1947 Jun 8 2 +-10 - HST +Z Pacific/Kanton 0 - -00 1937 Au 31 +-12 - -12 1979 O +-11 - -11 1994 D 31 +13 - +13 +Z Pacific/Kiritimati -10:29:20 - LMT 1901 +-10:40 - -1040 1979 O +-10 - -10 1994 D 31 +14 - +14 +Z Pacific/Kosrae -13:8:4 - LMT 1844 D 31 +10:51:56 - LMT 1901 +11 - +11 1914 O +9 - +09 1919 F +11 - +11 1937 +10 - +10 1941 Ap +9 - +09 1945 Au +11 - +11 1969 O +12 - +12 1999 +11 - +11 +Z Pacific/Kwajalein 11:9:20 - LMT 1901 +11 - +11 1937 +10 - +10 1941 Ap +9 - +09 1944 F 6 +11 - +11 1969 O +-12 - -12 1993 Au 20 24 +12 - +12 +Z Pacific/Marquesas -9:18 - LMT 1912 O +-9:30 - -0930 +Z Pacific/Nauru 11:7:40 - LMT 1921 Ja 15 +11:30 - +1130 1942 Au 29 +9 - +09 1945 S 8 +11:30 - +1130 1979 F 10 2 +12 - +12 +Z Pacific/Niue -11:19:40 - LMT 1952 O 16 +-11:20 - -1120 1964 Jul +-11 - -11 +Z Pacific/Norfolk 11:11:52 - LMT 1901 +11:12 - +1112 1951 +11:30 - +1130 1974 O 27 2s +11:30 1 +1230 1975 Mar 2 2s +11:30 - +1130 2015 O 4 2s +11 - +11 2019 Jul +11 AN +11/+12 +Z Pacific/Noumea 11:5:48 - LMT 1912 Ja 13 +11 NC +11/+12 +Z Pacific/Pago_Pago 12:37:12 - LMT 1892 Jul 5 +-11:22:48 - LMT 1911 +-11 - SST +Z Pacific/Palau -15:2:4 - LMT 1844 D 31 +8:57:56 - LMT 1901 +9 - +09 +Z Pacific/Pitcairn -8:40:20 - LMT 1901 +-8:30 - -0830 1998 Ap 27 +-8 - -08 +Z Pacific/Port_Moresby 9:48:40 - LMT 1880 +9:48:32 - PMMT 1895 +10 - +10 +Z Pacific/Rarotonga 13:20:56 - LMT 1899 D 26 +-10:39:4 - LMT 1952 O 16 +-10:30 - -1030 1978 N 12 +-10 CK -10/-0930 +Z Pacific/Tahiti -9:58:16 - LMT 1912 O +-10 - -10 +Z Pacific/Tarawa 11:32:4 - LMT 1901 +12 - +12 +Z Pacific/Tongatapu 12:19:12 - LMT 1945 S 10 +12:20 - +1220 1961 +13 - +13 1999 +13 TO +13/+14 +Z WET 0 E WE%sT +L Etc/GMT GMT L Australia/Sydney Australia/ACT L Australia/Lord_Howe Australia/LHI L Australia/Sydney Australia/NSW @@ -4185,7 +4195,6 @@ L Pacific/Port_Moresby Antarctica/DumontDUrville L Pacific/Auckland Antarctica/McMurdo L Asia/Riyadh Antarctica/Syowa -L Asia/Urumqi Antarctica/Vostok L Europe/Berlin Arctic/Longyearbyen L Asia/Riyadh Asia/Aden L Asia/Qatar Asia/Bahrain diff -Nru postgresql-13-13.13/src/tools/msvc/Solution.pm postgresql-13-13.14/src/tools/msvc/Solution.pm --- postgresql-13-13.13/src/tools/msvc/Solution.pm 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/tools/msvc/Solution.pm 2024-02-05 21:47:02.000000000 +0000 @@ -226,7 +226,6 @@ HAVE_ATOMICS => 1, HAVE_ATOMIC_H => undef, HAVE_BACKTRACE_SYMBOLS => undef, - HAVE_BIO_GET_DATA => undef, HAVE_BIO_METH_NEW => undef, HAVE_CLOCK_GETTIME => undef, HAVE_COMPUTED_GOTO => undef, @@ -543,7 +542,6 @@ || ($digit1 >= '1' && $digit2 >= '1' && $digit3 >= '0')) { $define{HAVE_ASN1_STRING_GET0_DATA} = 1; - $define{HAVE_BIO_GET_DATA} = 1; $define{HAVE_BIO_METH_NEW} = 1; $define{HAVE_OPENSSL_INIT_SSL} = 1; } diff -Nru postgresql-13-13.13/src/tools/pgindent/typedefs.list postgresql-13-13.14/src/tools/pgindent/typedefs.list --- postgresql-13-13.13/src/tools/pgindent/typedefs.list 2023-11-06 22:10:12.000000000 +0000 +++ postgresql-13-13.14/src/tools/pgindent/typedefs.list 2024-02-05 21:47:02.000000000 +0000 @@ -2447,6 +2447,7 @@ TSReadPointer TSTemplateInfo TSTernaryValue +TSTokenTypeItem TSTokenTypeStorage TSVector TSVectorBuildState