Modify pgbouncer.ini

Percona Everest
1

We’re currently facing an issue where we need to use schemas as part of regular migration activities on our postgres databases. We’re running into an issue with pgbouncer rejecting connections based upon them having search_path, and would ideally want to add search_path to the ignore_startup_parameters list.

Is there a way we can achieve this with our Everest-based clusters?

2

Hello @mbaba-03 - it is not supported yet.
We have the following ticket to resolve it: [EVEREST-139] - Percona JIRA

Meanwhile, you can have a workaround by editing a PG resource directly in k8s:

kubectl edit pg CLUSTER_NAME and alter spec.proxy.pgBouncer.config section.

1 Like