summaryrefslogtreecommitdiff
path: root/src/bin/pg_upgrade/controldata.c
diff options
context:
space:
mode:
authorMagnus Hagander2018-04-09 17:02:42 +0000
committerMagnus Hagander2018-04-09 17:03:42 +0000
commita228cc13aeabff308d6dfc98a1015865f5393fce (patch)
tree4704837fb075ccf7c8e5ecc10f341e527ed0e16d /src/bin/pg_upgrade/controldata.c
parent03c11796a95cc20a4559a103019d4d22a116a13c (diff)
Revert "Allow on-line enabling and disabling of data checksums"
This reverts the backend sides of commit 1fde38beaa0c3e66c340efc7cc0dc272d6254bb0. I have, at least for now, left the pg_verify_checksums tool in place, as this tool can be very valuable without the rest of the patch as well, and since it's a read-only tool that only runs when the cluster is down it should be a lot safer.
Diffstat (limited to 'src/bin/pg_upgrade/controldata.c')
-rw-r--r--src/bin/pg_upgrade/controldata.c9
1 files changed, 0 insertions, 9 deletions
diff --git a/src/bin/pg_upgrade/controldata.c b/src/bin/pg_upgrade/controldata.c
index 4bb2b7e6ec3..0fe98a550e1 100644
--- a/src/bin/pg_upgrade/controldata.c
+++ b/src/bin/pg_upgrade/controldata.c
@@ -591,15 +591,6 @@ check_control_data(ControlData *oldctrl,
*/
/*
- * If checksums have been turned on in the old cluster, but the
- * checksumhelper have yet to finish, then disallow upgrading. The user
- * should either let the process finish, or turn off checksums, before
- * retrying.
- */
- if (oldctrl->data_checksum_version == 2)
- pg_fatal("transition to data checksums not completed in old cluster\n");
-
- /*
* We might eventually allow upgrades from checksum to no-checksum
* clusters.
*/