postgres.git / summary / log / commit / refs
commit fbd2bd15b0114bb900aa6986add2b359fec1b740
Author: Tom Lane <tgl@sss.pgh.pa.us>
Date: Mon Sep 26 18:19:21 2022 +0000
First released in: 16.0, 15.0
Doc: further adjust notes about pg_upgrade_output.d.
I'd misunderstood how it worked in 5f1048881.
Discussion: https://postgr.es/m/20220925215009.GC21938@telsasoft.com
doc/src/sgml/ref/pgupgrade.sgml | 6 ++++--
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/doc/src/sgml/ref/pgupgrade.sgml b/doc/src/sgml/ref/pgupgrade.sgml
index 405999f6ad3..8f7a3025c36 100644
--- a/doc/src/sgml/ref/pgupgrade.sgml
+++ b/doc/src/sgml/ref/pgupgrade.sgml
@@ -773,8 +773,10 @@ psql --username=postgres --file=script.sql postgres
with a timestamp formatted as per ISO 8601
(<literal>%Y%m%dT%H%M%S</literal>), where all its generated files are
stored.
- <filename>pg_upgrade_output.d</filename> and all its contained files may be
- removed once the upgrade is successfully completed.
+ <filename>pg_upgrade_output.d</filename> and its contained files will be
+ removed automatically if <application>pg_upgrade</application> completes
+ successfully; but in the event of trouble, the files there may provide
+ useful debugging information.
</para>
<para>
[parent: 787102b56373]