From: Bruce Momjian Date: Wed, 3 Jun 2026 18:21:05 +0000 (-0400) Subject: doc PG 19 relnotes: merge pg_upgrade LO metadata items X-Git-Url: http://git.ipfire.org/gitweb/index.cgi?a=commitdiff_plain;h=378668d50b44afb52688988de6651aa8585f3f5c;p=thirdparty%2Fpostgresql.git doc PG 19 relnotes: merge pg_upgrade LO metadata items Also fix commit message cut/paste mistake, and add "tar" markup. --- diff --git a/doc/src/sgml/release-19.sgml b/doc/src/sgml/release-19.sgml index 3fb944e5681..7fdce6e46a5 100644 --- a/doc/src/sgml/release-19.sgml +++ b/doc/src/sgml/release-19.sgml @@ -403,6 +403,11 @@ Improve the planning of semijoins (Richard Guo) + + Allow Append and MergeAppend to consider explicit incremental sorts (Richard Guo) @@ -481,11 +486,6 @@ Simplify IS [NOT] TRUE/FALSE/UNKNOWN to plain boolean express - - + + + +Improve performance of pg_upgrade copying large object metadata (Nathan Bossart) +§ +§ +§ +§ + + + +Various methods are used, depending on the PostgreSQL version of the old cluster. + + + + + + + +Allow pg_upgrade to process non-default tablespaces stored in the PGDATA directory (Nathan Bossart) +§ + + + +Previously such tablespaces generated an error. + + + - - - -Have pg_upgrade copy large object metadata files rather than using COPY (Nathan Bossart) -§ -§ - - - -This is possible when upgrading from PostgreSQL 16 and later. - - - - - - - -Allow pg_upgrade to use COPY for large object metadata (Nathan Bossart) -§ - - - -This is used when upgrading from PostgreSQL major versions 12-15. - - - - - - - -Improve pg_upgrade performance when restoring large object metadata from PostgreSQL version 11 and earlier (Nathan Bossart) -§ - - - - - - - -Allow pg_upgrade to process non-default tablespaces stored in the PGDATA directory (Nathan Bossart) -§ - - - -Previously such tablespaces generated an error. - - - - - - - Logical Replication Applications