public_git/postgres-operator
1
0
Fork 0
mirror of https://github.com/zalando/postgres-operator.git synced 2026-10-03 09:36:57 +02:00
Code Issues Projects Releases Wiki Activity

finish PR1544

Browse Source
This commit is contained in:
Felix Kunde
2022-03-30 15:48:56 +02:00
parent cc10c3ea27
commit d78ccea3a8
8 changed files with 44 additions and 24 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/administrator.md
+9 -5
View File
@@ -1088,11 +1088,15 @@ data:
### Standby clusters
The setup for [standby clusters](user.md#setting-up-a-standby-cluster) is very
similar to cloning. At the moment, the operator only allows for streaming from
the S3 WAL archive of the master specified in the manifest. Like with cloning,
if you are using [additional environment variables](#custom-pod-environment-variables)
to access your backup location you have to copy those variables and prepend the
`STANDBY_` prefix for Spilo to find the backups and WAL files to stream.
similar to cloning. They can stream from a WAL archive (S3, GCS). Like with
cloning, if you are using [additional environment variables](#custom-pod-environment-variables)
to access your backup location you have to copy those variables and prepend
the `STANDBY_` prefix for Spilo to find the backups and WAL files to stream.
Alternatively, standby clusters can also stream from a remote primary cluster.
You have to specify the host address. Port is optional and defaults to 5432.
Note, that only one of the options (`s3_wal_path`, `gs_wal_path`,
`standby_host`) can be present under the `standby` top-level key.
## Logical backups
docs/reference/cluster_manifest.md
+5 -7
View File
@@ -395,24 +395,22 @@ 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. Either from a S3 or GCS WAL
archive or a remote primary. When both of them are set, `standby_host`
takes precedence.
cluster streaming from a remote location - either from a S3 or GCS WAL
archive or a remote primary. Only one of options is allowed and required
if the `standby` key is present.
* **s3_wal_path**
the url to S3 bucket containing the WAL archive of the remote primary.
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.
TCP port on which the primary is listening for connections. Patroni will
use `"5432"` if not set.
## Volume properties