diff options
| author | Michael Paquier <michael@paquier.xyz> | 2023-12-04 08:10:27 +0900 |
|---|---|---|
| committer | Michael Paquier <michael@paquier.xyz> | 2023-12-04 08:10:27 +0900 |
| commit | 0e4674a697d5bdb9f3136005f0467c874b28e6d7 (patch) | |
| tree | 1c6ce65fc61e0d988a69c704747ee78851d4775c /doc/src | |
| parent | 15d485921b1c2125d551e87a1f04be9d5c124b15 (diff) | |
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.sgml | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/doc/src/sgml/high-availability.sgml b/doc/src/sgml/high-availability.sgml index e4f49031baf..7aa6fefbef3 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> |
