From 3a2906545f839aaf3a49f08a6f8d2cb1f841168f Mon Sep 17 00:00:00 2001 From: Bruce Momjian Date: Thu, 23 Jun 2011 19:57:45 -0400 Subject: [PATCH] In pg_upgrade docs, clarify that link mode uses "hard" links. Backpatch to 9.1 and 9.0. --- doc/src/sgml/pgupgrade.sgml | 20 ++++++++++++-------- 1 file changed, 12 insertions(+), 8 deletions(-) diff --git a/doc/src/sgml/pgupgrade.sgml b/doc/src/sgml/pgupgrade.sgml index bf5f40bf5a..8e975d8e20 100644 --- a/doc/src/sgml/pgupgrade.sgml +++ b/doc/src/sgml/pgupgrade.sgml @@ -91,7 +91,7 @@ - link instead of copying files to new cluster + use hard links instead of copying files to the new cluster @@ -276,14 +276,18 @@ NET STOP pgsql-8.3 (PostgreSQL 8.3 and older used a different s Always run the pg_upgrade binary of the new server, not the old one. pg_upgrade requires the specification of the old and new cluster's - data and executable (bin) directories. You can also specify separate + data and executable (bin) directories. You can also specify user and port values, and whether you want the data linked instead of - copied (the default). If you use linking, the migration will be much - faster (hard link data files rather than copying them), but you - will no longer be able to access your old cluster once you start - the new cluster after the upgrade. Link mode also requires that the - old and new cluster data directories be in the same file system. - See pg_upgrade --help for a full list of options. + copied (the default). + + + + If you use link mode, the upgrade will be much faster (no file + copying), but you will not be able to access your old cluster + once you start the new cluster after the upgrade. Link mode also + requires that the old and new cluster data directories be in the + same file system. See pg_upgrade --help for a full + list of options. -- 2.40.0