summaryrefslogtreecommitdiff
path: root/src/backend/replication
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/replication
parentd6391b03b3025372620925e5746e65c288a1e371 (diff)
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/replication')
-rw-r--r--src/backend/replication/walsender.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/backend/replication/walsender.c b/src/backend/replication/walsender.c
index 9a2babef1e6..03e1cf44dee 100644
--- a/src/backend/replication/walsender.c
+++ b/src/backend/replication/walsender.c
@@ -2572,7 +2572,7 @@ XLogSendPhysical(void)
* fsync'd to disk. We cannot go further than what's been written out
* given the current implementation of XLogRead(). And in any case
* it's unsafe to send WAL that is not securely down to disk on the
- * master: if the master subsequently crashes and restarts, slaves
+ * master: if the master subsequently crashes and restarts, standbys
* must not have applied any WAL that got lost on the master.
*/
SendRqstPtr = GetFlushRecPtr();