Removed requirements wal_log_hints = on for pg_arman work.

stalkerg · stalkerg · commit 324efc064ffe · 2016-11-10T16:32:02.000+03:00
diff --git a/README.md b/README.md
@@ -102,7 +102,6 @@ You need to enable WAL archive by adding following lines to postgresql.conf:
 ```
 wal_level = archive
 archive_command = 'test ! -f /home/postgres/backup/arman/wal/%f && cp %p /home/postgres/backup/arman/wal/%f'
-wal_log_hints = on
 ```
 
 Example backup (assuming PostgreSQL is running):
diff --git a/doc/pg_arman.md b/doc/pg_arman.md
@@ -389,8 +389,6 @@ are required if the value contains whitespaces. Comments should start with
 excluding values.
 
 ### RESTRICTIONS
-* In order to work, the PostgreSQL instance on which backups are taken need
-to have data checksums enabled or to enable wal_log_hints.
 * pg_arman is aimed at working with PostgreSQL 9.5 and newer versions.
 * For ptrack feature you need special version of Postgres and set wal_level to
 archive or hot_standby and ptrack_enable.
diff --git a/sql/common.sh b/sql/common.sh
@@ -70,7 +70,7 @@ function init_backup()
 port = ${TEST_PGPORT}
 logging_collector = on
 wal_level = hot_standby
-wal_log_hints = on
+wal_log_hints = off
 archive_mode = on
 archive_command = 'cp %p ${ARCLOG_PATH}/%f'
 ptrack_enable = on
diff --git a/util.c b/util.c
@@ -84,15 +84,6 @@ sanityChecks(void)
 	digestControlFile(&ControlFile, buffer, size);
 	pg_free(buffer);
 
-	/*
-	 * Node work is done on need to use checksums or hint bit wal-logging
-	 * this to prevent from data corruption that could occur because of
-	 * hint bits.
-	 */
-	if (ControlFile.data_checksum_version != PG_DATA_CHECKSUM_VERSION &&
-		!ControlFile.wal_log_hints)
-		elog(ERROR,
-			 "target master need to use either data checksums or \"wal_log_hints = on\".");
 }
 
 XLogRecPtr
