add the possibility to create a standby cluster that streams from a remote primary

This commit is contained in:
machine424
2022-03-11 13:16:46 +01:00
parent ca0c27a51b
commit eb990fd456
8 changed files with 150 additions and 36 deletions
+11 -3
View File
@@ -385,17 +385,25 @@ under the `clone` top-level key and do not affect the already running cluster.
## Standby cluster
On startup, an existing `standby` top-level key creates a standby Postgres
cluster streaming from a remote location. So far streaming from S3 and GCS WAL
archives is supported.
cluster streaming from a remote location. Either from a S3 or GCS WAL
archive or a remote primary. When both of them are set, `standby_host`
takes precedence.
* **s3_wal_path**
the url to S3 bucket containing the WAL archive of the remote primary.
Optional, but `s3_wal_path` or `gs_wal_path` is required.
Required when the `standby` section is present even when `standby_host` is set.
* **gs_wal_path**
the url to GS bucket containing the WAL archive of the remote primary.
Optional, but `s3_wal_path` or `gs_wal_path` is required.
* **standby_host**
hostname or IP address of the primary to stream from.
When set, `s3_wal_path` is ignored.
* **standby_port**
TCP port on which the primary is listening for connections.
## Volume properties
Those parameters are grouped under the `volume` top-level key and define the