aboutsummaryrefslogtreecommitdiff
path: root/doc/src
diff options
context:
space:
mode:
authorMichael Paquier <michael@paquier.xyz>2023-12-04 08:09:51 +0900
committerMichael Paquier <michael@paquier.xyz>2023-12-04 08:09:51 +0900
commitd78b6cbb602f5c36db3e267e2713b3aa22c815a5 (patch)
tree33161cb512460b584eb33eb475ac746ad853e89a /doc/src
parentfd5e8b440dfd633be74e3dd3382d4a9038dba24f (diff)
downloadpostgresql-d78b6cbb602f5c36db3e267e2713b3aa22c815a5.tar.gz
postgresql-d78b6cbb602f5c36db3e267e2713b3aa22c815a5.zip
doc: Remove reference to trigger file regarding promotion
The wording changed here comes from 991bfe11d28a, when the only way to trigger a promotion was with a trigger file. There are more options to achieve this operation these days, like the SQL function pg_promote() or the command `pg_ctl promote`, so it is confusing to assume that only a trigger file is able to do the work. Note also that promote_trigger_file has been removed as of cd4329d9393f in 16~. Author: Shinya Kato Discussion: https://postgr.es/m/201b08ea29aa61f96162080e75be503c@oss.nttdata.com Backpatch-through: 12
Diffstat (limited to 'doc/src')
-rw-r--r--doc/src/sgml/high-availability.sgml2
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml
index eb81260bbf1..9dd52ff2750 100644
--- a/doc/src/sgml/high-availability.sgml
+++ b/doc/src/sgml/high-availability.sgml
@@ -648,7 +648,7 @@ protocol to make nodes agree on a serializable transactional order.
later disconnected, the standby goes back to step 1 and tries to
restore the file from the archive again. This loop of retries from the
archive, <filename>pg_wal</filename>, and via streaming replication goes on until the server
- is stopped or failover is triggered by a trigger file.
+ is stopped or is promoted.
</para>
<para>