public_git
/
postgres-operator
mirror of https://github.com/zalando/postgres-operator.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity

address review comments

This commit is contained in:
Felix Kunde 2019-07-10 17:27:23 +02:00
parent 0775e0d5d6
commit 1b2ce33d69
3 changed files with 11 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
README.md
View File

@ -38,12 +38,9 @@ There is a browser-friendly version of this documentation at
## Google Summer of Code ## Google Summer of Code
The Postgres Operator made it to the [Google Summer of Code 2019](https://summerofcode.withgoogle.com/)! The Postgres Operator made it to the [Google Summer of Code 2019](https://summerofcode.withgoogle.com/organizations/5429926902104064/)!
As a brand new mentoring organization, we are now looking for our first mentees.
Check [our ideas](docs/gsoc-2019/ideas.md#google-summer-of-code-2019) Check [our ideas](docs/gsoc-2019/ideas.md#google-summer-of-code-2019)
and start discussion in [the issue tracker](https://github.com/zalando/postgres-operator/issues). and start discussions in [the issue tracker](https://github.com/zalando/postgres-operator/issues).
And don't forget to spread a word about our GSoC participation to attract even
more students.
## Community ## Community

12
docs/quickstart.md
View File

@ -166,8 +166,10 @@ kubectl delete postgresql acid-minimal-cluster
This should remove the associated StatefulSet, database Pods, Services and This should remove the associated StatefulSet, database Pods, Services and
Endpoints. The PersistentVolumes are released and the PodDisruptionBudget is Endpoints. The PersistentVolumes are released and the PodDisruptionBudget is
deleted. Secrets however are not deleted. When deleting a cluster while it is deleted. Secrets however are not deleted and backups will remain in place.
still starting up it can [happen](https://github.com/zalando/postgres-operator/issues/551)
the `postgresql` resource is deleted leaving orphaned components behind. This When deleting a cluster while it is still starting up or got stuck during that
can cause troubles when creating a new Postgres cluster. For a fresh setup you phase it can [happen](https://github.com/zalando/postgres-operator/issues/551)
can delete your local minikube or kind cluster and start again. that the `postgresql` resource is deleted leaving orphaned components behind.
This can cause troubles when creating a new Postgres cluster. For a fresh setup
you can delete your local minikube or kind cluster and start again.

5
docs/reference/cluster_manifest.md
View File

@ -153,8 +153,7 @@ required in the manifest.
* **parameters** * **parameters**
a dictionary of Postgres parameter names and values to apply to the resulting a dictionary of Postgres parameter names and values to apply to the resulting
cluster. Optional (Spilo automatically sets reasonable defaults for parameters cluster. Optional (Spilo automatically sets reasonable defaults for parameters
like work_mem or max_connections). like `work_mem` or `max_connections`).
## Patroni parameters ## Patroni parameters
@ -198,7 +197,7 @@ explanation of `ttl` and `loop_wait` parameters.
* **slots** * **slots**
permanent replication slots that Patroni preserves after failover by permanent replication slots that Patroni preserves after failover by
re-creating them on the new primary immediately after doing a promote. Slots re-creating them on the new primary immediately after doing a promote. Slots
could be reconfigured with the help of `Patronictl edit-config`. It is the could be reconfigured with the help of `patronictl edit-config`. It is the
responsibility of a user to avoid clashes in names between replication slots responsibility of a user to avoid clashes in names between replication slots
automatically created by Patroni for cluster members and permanent replication automatically created by Patroni for cluster members and permanent replication
slots. Optional. slots. Optional.