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/commands/variable.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'src/backend/commands/variable.c') diff --git a/src/backend/commands/variable.c b/src/backend/commands/variable.c index 4156bcd8dfa..3ed1c56e827 100644 --- a/src/backend/commands/variable.c +++ b/src/backend/commands/variable.c @@ -472,8 +472,8 @@ show_log_timezone(void) * We allow idempotent changes (r/w -> r/w and r/o -> r/o) at any time, and * we also always allow changes from read-write to read-only. However, * read-only may be changed to read-write only when in a top-level transaction - * that has not yet taken an initial snapshot. Can't do it in a hot standby - * slave, either. + * that has not yet taken an initial snapshot. Can't do it in a hot standby, + * either. * * If we are not in a transaction at all, just allow the change; it means * nothing since XactReadOnly will be reset by the next StartTransaction(). -- cgit v1.2.3