aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBruce Momjian <bruce@momjian.us>2013-01-31 16:32:35 -0500
committerBruce Momjian <bruce@momjian.us>2013-01-31 16:32:35 -0500
commita11e15c7b66c647269ecad73560be0e717ffc400 (patch)
treef1589167770872c52369260d9e5318560e9a7e3e
parent3f0ab052330905f1ad2183684e75e6a2cbfa0c76 (diff)
downloadpostgresql-a11e15c7b66c647269ecad73560be0e717ffc400.tar.gz
postgresql-a11e15c7b66c647269ecad73560be0e717ffc400.zip
pg_upgrade docs: mention modification of postgresql.conf in new cluster
Mention it might be necessary to modify postgresql.conf in the new cluster to match the old cluster. Backpatch to 9.2. Suggested by user.
-rw-r--r--doc/src/sgml/pgupgrade.sgml4
1 files changed, 3 insertions, 1 deletions
diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml
index e0765babfc5..5baf420a27a 100644
--- a/doc/src/sgml/pgupgrade.sgml
+++ b/doc/src/sgml/pgupgrade.sgml
@@ -402,7 +402,9 @@ pg_upgrade.exe
<para>
If you modified <filename>pg_hba.conf</> to use <literal>trust</>,
- restore its original authentication settings.
+ restore its original authentication settings. It might also be
+ necessary to adjust other configurations files in the new cluster to
+ match the old cluster, e.g. <filename>postgresql.conf</>.
</para>
</step>