diff options
| author | Peter Eisentraut | 2016-03-01 01:01:54 +0000 |
|---|---|---|
| committer | Peter Eisentraut | 2016-03-18 22:56:03 +0000 |
| commit | b555ed8102672cfedb06559952b8341756386d69 (patch) | |
| tree | 6e3174c6e0bcd2faee09307092ecdca5dd0169b9 /src/backend/replication/slot.c | |
| parent | 4e1d2a170836028370675922ea9a690648d3c18d (diff) | |
Merge wal_level "archive" and "hot_standby" into new name "replica"
The distinction between "archive" and "hot_standby" existed only because
at the time "hot_standby" was added, there was some uncertainty about
stability. This is now a long time ago. We would like to move forward
with simplifying the replication configuration, but this distinction is
in the way, because a primary server cannot tell (without asking a
standby or predicting the future) which one of these would be the
appropriate level.
Pick a new name for the combined setting to make it clearer that it
covers all (non-logical) backup and replication uses. The old values
are still accepted but are converted internally.
Reviewed-by: Michael Paquier <[email protected]>
Reviewed-by: David Steele <[email protected]>
Diffstat (limited to 'src/backend/replication/slot.c')
| -rw-r--r-- | src/backend/replication/slot.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/replication/slot.c b/src/backend/replication/slot.c index ead221d3c75..c13be753ea9 100644 --- a/src/backend/replication/slot.c +++ b/src/backend/replication/slot.c @@ -760,7 +760,7 @@ CheckSlotRequirements(void) (errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE), (errmsg("replication slots can only be used if max_replication_slots > 0")))); - if (wal_level < WAL_LEVEL_ARCHIVE) + if (wal_level < WAL_LEVEL_REPLICA) ereport(ERROR, (errcode(ERRCODE_OBJECT_NOT_IN_PREREQUISITE_STATE), errmsg("replication slots can only be used if wal_level >= archive"))); |