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.
This commit is contained in:
Robert Haas 2011-03-23 11:44:27 -04:00
parent b98ac467f5
commit 19584ec659

View File

@ -735,9 +735,6 @@ PostmasterMain(int argc, char *argv[])
if (max_wal_senders > 0 && wal_level == WAL_LEVEL_MINIMAL) if (max_wal_senders > 0 && wal_level == WAL_LEVEL_MINIMAL)
ereport(ERROR, ereport(ERROR,
(errmsg("WAL streaming (max_wal_senders > 0) requires wal_level \"archive\" or \"hot_standby\""))); (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. * Other one-time internal sanity checks can go here, if they are fast.