Commit4624228

committed

In pg_upgrade 9.0 and 9.1, document suggestion of using a non-default

port number to avoid unintended client connections.

1 parentbbfcc71 commit4624228Copy full SHA for 4624228

File tree

-2

lines changed

-2

lines changed

Lines changed: 4 additions & 2 deletions

Original file line number	Diff line number	Diff line change
`@@ -239,8 +239,7 @@ gmake prefix=/usr/local/pgsql.new install`
`239`	`239`	`so you might want to set authentication to <literal>trust</> in`
`240`	`240`	`<filename>pg_hba.conf</>, or if using <literal>md5</> authentication,`
`241`	`241`	`use a <filename>~/.pgpass</> file (see <xref linkend="libpq-pgpass">)`
`242`		`- to avoid being prompted repeatedly for a password. Also make sure`
`243`		`- pg_upgrade is the only program that can connect to the clusters.`
	`242`	`+ to avoid being prompted repeatedly for a password.`
`244`	`243`	`</para>`
`245`	`244`	`</step>`
`246`	`245`
`@@ -319,6 +318,9 @@ pg_upgrade.exe`
`319`	`318`
`320`	`319`	`<para>`
`321`	`320`	`Obviously, no one should be accessing the clusters during the migration.`
	`321`	`+ Consider using a non-default port number, e.g. 50432, for old`
	`322`	`+ and new clusters to avoid unintended client connections during`
	`323`	`+ the upgrade.`
`322`	`324`	`</para>`
`323`	`325`
`324`	`326`	`<para>`

Comments

(0)