From 5f1048881d5f16475b76e168bfe962682c741fb5 Mon Sep 17 00:00:00 2001 From: Tom Lane Date: Fri, 23 Sep 2022 18:20:11 -0400 Subject: [PATCH] Doc: minor cleanups. Improve a couple of things I noticed while working on v15 release notes. --- doc/src/sgml/config.sgml | 7 ++++--- doc/src/sgml/ref/pgupgrade.sgml | 6 ++++-- 2 files changed, 8 insertions(+), 5 deletions(-) diff --git a/doc/src/sgml/config.sgml b/doc/src/sgml/config.sgml index e75181ba75..d8848bc774 100644 --- a/doc/src/sgml/config.sgml +++ b/doc/src/sgml/config.sgml @@ -10838,9 +10838,10 @@ dynamic_library_path = 'C:\tools\postgresql;H:\my_project\lib;$libdir' will accept a setting for any two-part parameter name. Such variables are treated as placeholders and have no function until the module that defines them is loaded. When an extension module is loaded, it will add - its variable definitions, convert any placeholder values according to - those definitions, and issue warnings for any unrecognized placeholders - that begin with its extension name. + its variable definitions and convert any placeholder values according to + those definitions. If there are any unrecognized placeholders + that begin with its extension name, warnings are issued and those + placeholders are removed. diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml index 26459f7e91..405999f6ad 100644 --- a/doc/src/sgml/ref/pgupgrade.sgml +++ b/doc/src/sgml/ref/pgupgrade.sgml @@ -768,11 +768,13 @@ psql --username=postgres --file=script.sql postgres pg_upgrade creates various working files, such - as schema dumps, stored within pg_upgrade_output.d in + as schema dumps, stored within pg_upgrade_output.d in the directory of the new cluster. Each run creates a new subdirectory named with a timestamp formatted as per ISO 8601 - (%Y%m%dT%H%M%S), where all the generated files are + (%Y%m%dT%H%M%S), where all its generated files are stored. + pg_upgrade_output.d and all its contained files may be + removed once the upgrade is successfully completed.