Hi,
I would like to set custom parameters for pgbouncer like for postgres
Is it possible do it in code instead of modify specific config map and restart pgbouncer pods?
Thanks in advance
Hi,
I would like to set custom parameters for pgbouncer like for postgres
Is it possible do it in code instead of modify specific config map and restart pgbouncer pods?
Thanks in advance
Hi @Viktor_Kucher,
Why do you want to change operator code for customizing pgbouncer?
for example max_client_conn because default value is 100 and I would like to increase it.
I understand why you want to customize pgbouncer configuration. But doing it in the code means you’ll maintain your own fork for this customization. Are there anything that blocks you from creating a config map?
Of course I can update config map for pgbouncer and restart pgbouncer. Percona operator supports custom config map for pgCluster, like
spec:
…
pgPrimary:
…
customconfig: “cluster1-custom-config”
.
is it possible to use custom configuration for pgbouncer ?
Unanswered | Unsolved | Solved
MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners.
Copyright © 2006 - 2024 Percona LLC. All rights reserved.