Postgres-operator: patroni boostrap options synchronous_mode (and others)

Created on 28 Feb 2019  路  4Comments  路  Source: zalando/postgres-operator

This might fall in a feature request list.

I am trying to setup synchronous_mode. For now the operator does not expose this patroni bootstrap option. This is similar to: #428

Initially I expected that entire spec/patroni gets passed to patroni boostrap, but I was wrong.
If this direction is not possible, will there be an option to pass another map of params from the cluster definition directly to patroni boostrap, without requiring code changes in the operator to interpreting every field?
Or, are there any other options to control patroni from my cluster request?

patroni question

Most helpful comment

@FxKu @siku4 cool, will make the PR in the next day or so

All 4 comments

piggybacking off this question.

I鈥檇 like to request adding synchronous_mode type fields. I鈥檝e exposed both synchronous_mode and synchronous_mode_strict in my branch that seems to work and I'd like to contribute. However, I鈥檓 still relatively new to how _patroni_ works and maybe this is why it has been excluded?

I am also very interested in this issue.

@jecho I took a look at your fork (this commit, right?) and it looks good. Have you already tested it in production and made a pull request?

@jecho +1 for opening a PR. When adding manifest fields they have to be covered by CRD validation as well, but I will guide you then.

@FxKu @siku4 cool, will make the PR in the next day or so

Was this page helpful?
0 / 5 - 0 ratings

Related issues

valer-cara picture valer-cara  路  5Comments

michailbrynard picture michailbrynard  路  6Comments

hedgss picture hedgss  路  3Comments

k0da picture k0da  路  4Comments

aixeshunter picture aixeshunter  路  6Comments