From: Robert Haas <rhaas@postgresql.org>
Date: Wed, 23 Mar 2011 15:44:27 +0000 (-0400)
Subject: Remove synchronous_replication/max_wal_senders cross-check.
X-Git-Tag: REL9_1_ALPHA5~29
X-Git-Url: https://granicus.if.org/sourcecode?a=commitdiff_plain;h=19584ec659678841ea3036336f960acbdae962a0;p=postgresql

Remove synchronous_replication/max_wal_senders cross-check.

This is no longer necessary, and might result in a situation where the
configuration file is reloaded (and everything seems OK) but a subsequent
restart of the database fails.

Per an observation from Fujii Masao.
---

diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
index 47c81e4db1..997af5bf07 100644
--- a/src/backend/postmaster/postmaster.c
+++ b/src/backend/postmaster/postmaster.c
@@ -735,9 +735,6 @@ PostmasterMain(int argc, char *argv[])
 	if (max_wal_senders > 0 && wal_level == WAL_LEVEL_MINIMAL)
 		ereport(ERROR,
 				(errmsg("WAL streaming (max_wal_senders > 0) requires wal_level \"archive\" or \"hot_standby\"")));
-	if (strlen(SyncRepStandbyNames) > 0 && max_wal_senders == 0)
-		ereport(ERROR,
-				(errmsg("synchronous replication requires WAL streaming (max_wal_senders > 0)")));
 
 	/*
 	 * Other one-time internal sanity checks can go here, if they are fast.