|
182 | 182 |
|
183 | 183 | <para>
|
184 | 184 | If you are using a version-specific installation directory, e.g.
|
185 |
| - <filename>/opt/PostgreSQL/8.4</>, you do not need to move the old cluster. The |
| 185 | + <filename>/opt/PostgreSQL/9.1</>, you do not need to move the old cluster. The |
186 | 186 | one-click installers all use version-specific installation directories.
|
187 | 187 | </para>
|
188 | 188 |
|
@@ -254,7 +254,8 @@ gmake prefix=/usr/local/pgsql.new install
|
254 | 254 |
|
255 | 255 | <para>
|
256 | 256 | Install any custom shared object files (or DLLs) used by the old cluster
|
257 |
| - into the new cluster, e.g. <filename>pgcrypto.so</filename>, whether they are from <filename>contrib</filename> |
| 257 | + into the new cluster, e.g. <filename>pgcrypto.so</filename>, |
| 258 | + whether they are from <filename>contrib</filename> |
258 | 259 | or some other source. Do not install the schema definitions, e.g.
|
259 | 260 | <filename>pgcrypto.sql</>, because these will be upgraded from the old cluster.
|
260 | 261 | </para>
|
@@ -454,18 +455,14 @@ psql --username postgres --file script.sql postgres
|
454 | 455 |
|
455 | 456 | <listitem>
|
456 | 457 | <para>
|
457 |
| - If you |
458 |
| - ran <command>pg_upgrade</command> <emphasis>without</> <option>--link</> |
459 |
| - or did not start the new server, the old cluster was not |
460 |
| - modified except that an <literal>.old</> suffix was appended |
461 |
| - to <filename>$PGDATA/global/pg_control</> and perhaps |
462 |
| - tablespace directories. To reuse the old cluster, remove |
463 |
| - the <filename>.old</> suffix |
464 |
| - from <filename>$PGDATA/global/pg_control</>. and, if upgrading |
465 |
| - to 8.4 or earlier, remove the tablespace directories created |
466 |
| - by the upgrade and remove the <filename>.old</> suffix from |
467 |
| - the tablespace directory names; then you can restart the old |
468 |
| - cluster. |
| 458 | + If you ran <command>pg_upgrade</command> <emphasis>without</> |
| 459 | + <option>--link</> or did not start the new server, the |
| 460 | + old cluster was not modified except that, if linking |
| 461 | + started, a <literal>.old</> suffix was appended to |
| 462 | + <filename>$PGDATA/global/pg_control</>. To reuse the old |
| 463 | + cluster, possibly remove the <filename>.old</> suffix from |
| 464 | + <filename>$PGDATA/global/pg_control</>; you can then restart the |
| 465 | + old cluster. |
469 | 466 | </para>
|
470 | 467 | </listitem>
|
471 | 468 | </itemizedlist>
|
@@ -582,9 +579,9 @@ psql --username postgres --file script.sql postgres
|
582 | 579 | </para>
|
583 | 580 |
|
584 | 581 | <para>
|
585 |
| - If you want to use link mode and you don't want your old cluster |
| 582 | + If you want to use link mode and you do not want your old cluster |
586 | 583 | to be modified when the new cluster is started, make a copy of the
|
587 |
| - old cluster and upgrade that with link mode. To make a valid copy |
| 584 | + old cluster and upgrade that in link mode. To make a valid copy |
588 | 585 | of the old cluster, use <command>rsync</> to create a dirty
|
589 | 586 | copy of the old cluster while the server is running, then shut down
|
590 | 587 | the old server and run <command>rsync</> again to update the copy with any
|
|
0 commit comments