From a1ef920e27ba6ab3602aaf6d6751d8628fac1af8 Mon Sep 17 00:00:00 2001 From: Peter Eisentraut Date: Mon, 7 Aug 2017 17:42:47 -0400 Subject: Remove uses of "slave" in replication contexts This affects mostly code comments, some documentation, and tests. Official APIs already used "standby". --- src/backend/access/transam/commit_ts.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'src/backend/access/transam/commit_ts.c') diff --git a/src/backend/access/transam/commit_ts.c b/src/backend/access/transam/commit_ts.c index 827d976db83..60fb9eeb061 100644 --- a/src/backend/access/transam/commit_ts.c +++ b/src/backend/access/transam/commit_ts.c @@ -621,7 +621,7 @@ CommitTsParameterChange(bool newvalue, bool oldvalue) * * The reason why this SLRU needs separate activation/deactivation functions is * that it can be enabled/disabled during start and the activation/deactivation - * on master is propagated to slave via replay. Other SLRUs don't have this + * on master is propagated to standby via replay. Other SLRUs don't have this * property and they can be just initialized during normal startup. * * This is in charge of creating the currently active segment, if it's not -- cgit v1.2.3