database/postgres
1
0
Fork 0
mirror of https://github.com/postgres/postgres.git synced 2025-06-13 07:41:39 +03:00
Code Activity

Remove uses of "slave" in replication contexts

Browse Source 
This affects mostly code comments, some documentation, and tests.
Official APIs already used "standby".
This commit is contained in:
Peter Eisentraut
2017-08-07 17:42:47 -04:00
parent d6391b03b3
commit a1ef920e27
21 changed files with 103 additions and 103 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
doc/src/sgml/high-availability.sgml
View File

@ -40,7 +40,7 @@
server to modify the data. Servers that can modify data are
called read/write, <firstterm>master</> or <firstterm>primary</> servers.
Servers that track changes in the master are called <firstterm>standby</>
or <firstterm>slave</> servers. A standby server that cannot be connected
or <firstterm>secondary</> servers. A standby server that cannot be connected
to until it is promoted to a master server is called a <firstterm>warm
standby</> server, and one that can accept connections and serves read-only
queries is called a <firstterm>hot standby</> server.

4
doc/src/sgml/ref/pgupgrade.sgml
View File

@ -483,7 +483,7 @@ pg_upgrade.exe
<para>
From a directory that is above the old and new database cluster
directories, run this for each slave:
directories, run this for each standby:
<programlisting>
rsync --archive --delete --hard-links --size-only old_pgdata new_pgdata remote_dir
@ -517,7 +517,7 @@ rsync --archive --delete --hard-links --size-only old_pgdata new_pgdata remote_d
<para>
Configure the servers for log shipping. (You do not need to run
<function>pg_start_backup()</> and <function>pg_stop_backup()</>
or take a file system backup as the slaves are still synchronized
or take a file system backup as the standbys are still synchronized
with the master.)
</para>
</step>