aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlvaro Herrera <alvherre@alvh.no-ip.org>2012-08-27 14:20:28 -0400
committerAlvaro Herrera <alvherre@alvh.no-ip.org>2012-08-27 14:29:14 -0400
commit34c02044ed7e7defde5a853b26dcd806c872d974 (patch)
treed9db3012d873e996e300350706eccc941938985a
parentab577e63faf792593ca728625a8ef0b1dfaf7500 (diff)
downloadpostgresql-34c02044ed7e7defde5a853b26dcd806c872d974.tar.gz
postgresql-34c02044ed7e7defde5a853b26dcd806c872d974.zip
Fix thinko in comment
It was confusing symlinks with hard links.
-rw-r--r--contrib/pg_upgrade/file.c4
1 files changed, 2 insertions, 2 deletions
diff --git a/contrib/pg_upgrade/file.c b/contrib/pg_upgrade/file.c
index 550967009b3..a5d92c62fce 100644
--- a/contrib/pg_upgrade/file.c
+++ b/contrib/pg_upgrade/file.c
@@ -103,10 +103,10 @@ copyAndUpdateFile(pageCnvCtx *pageConverter,
/*
* linkAndUpdateFile()
*
- * Creates a symbolic link between the given relation files. We use
+ * Creates a hard link between the given relation files. We use
* this function to perform a true in-place update. If the on-disk
* format of the new cluster is bit-for-bit compatible with the on-disk
- * format of the old cluster, we can simply symlink each relation
+ * format of the old cluster, we can simply link each relation
* instead of copying the data from the old cluster to the new cluster.
*/
const char *