aboutsummaryrefslogtreecommitdiff
path: root/src/backend/commands/variable.c
diff options
context:
space:
mode:
authorPeter Eisentraut <peter_e@gmx.net>2017-08-07 17:42:47 -0400
committerPeter Eisentraut <peter_e@gmx.net>2017-08-10 22:55:41 -0400
commita1ef920e27ba6ab3602aaf6d6751d8628fac1af8 (patch)
tree51485b2898ae4b01b2e71ad5e40a7d3b02d75f91 /src/backend/commands/variable.c
parentd6391b03b3025372620925e5746e65c288a1e371 (diff)
downloadpostgresql-a1ef920e27ba6ab3602aaf6d6751d8628fac1af8.tar.gz
postgresql-a1ef920e27ba6ab3602aaf6d6751d8628fac1af8.zip
Remove uses of "slave" in replication contexts
This affects mostly code comments, some documentation, and tests. Official APIs already used "standby".
Diffstat (limited to 'src/backend/commands/variable.c')
-rw-r--r--src/backend/commands/variable.c4
1 files changed, 2 insertions, 2 deletions
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().