aboutsummaryrefslogtreecommitdiff
path: root/src/backend
diff options
context:
space:
mode:
authorRobert Haas <rhaas@postgresql.org>2011-03-23 11:44:27 -0400
committerRobert Haas <rhaas@postgresql.org>2011-03-23 11:44:27 -0400
commit19584ec659678841ea3036336f960acbdae962a0 (patch)
treef0fb8ce49fa941c7dccdb4ecadcea4d05fd68a88 /src/backend
parentb98ac467f5d35970edade4ad65c767fc89059026 (diff)
downloadpostgresql-19584ec659678841ea3036336f960acbdae962a0.tar.gz
postgresql-19584ec659678841ea3036336f960acbdae962a0.zip
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.
Diffstat (limited to 'src/backend')
-rw-r--r--src/backend/postmaster/postmaster.c3
1 files changed, 0 insertions, 3 deletions
diff --git a/src/backend/postmaster/postmaster.c b/src/backend/postmaster/postmaster.c
index 47c81e4db1b..997af5bf072 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.