Is there an existing issue already for this feature request/idea?

• I have searched for an existing issue, and could not find anything. I believe this is a new feature request to be evaluated.

What problem is this feature going to solve? Why should it be added?

At this moment the operator is generating the primary_conninfo PostgreSQL parameter, and the user has no way to inject any custom parameter into that.

Allowing that can be useful to adapt the configuration to the environment where the cluster is deployed, i.e. setting the tcp_user_timeout appropriately.

Describe the solution you'd like

I'd like to have a new field in the API, named spec.postgresql.standbyConnectionParameters where the user can inject custom configurations.

Describe alternatives you've considered

n.a.

Additional context

No response

Backport?

No

Are you willing to actively contribute to this feature?

Yes

Code of Conduct

• I agree to follow this project's Code of Conduct