a1f2bd05b9
* Protected and system users can't be a connection pool user It's not supported, neither it's a best practice. Also fix potential null pointer access. For protected users it makes sense by intent of protecting this users (e.g. from being overriden or used as something else than supposed). For system users the reason is the same as for superuser, it's about replicastion user and it's under patroni control. This is implemented on both levels, operator config and postgresql manifest. For the latter we just use default name in this case, assuming that operator config is always correct. For the former, since it's a serious misconfiguration, operator panics. |
||
|---|---|---|
| .. | ||
| apis/acid.zalan.do | ||
| apiserver | ||
| cluster | ||
| controller | ||
| generated | ||
| spec | ||
| util | ||