pg bouncer

[Bjoern_ch]

Hi veeam team,
Hi all,

we currently have no pg bouncer in use yet although we have more than 40 proxies in use. In general, it is working fine. But now we have several support cases open where supports recommends to deploy pg bouncer.
So, we followed the kb articles:
https://www.veeam.com/kb4728
https://www.veeam.com/kb4758
But, unfortunately, we cannot deploy it successfully. Support cannot help on that for quite some time.
After we finished all steps from the guides we are now in the process of editing the postgres user in the proxy.xml. But the changes are not persistent. With this change it is working. But every time the services restarts the changes are revoked and the proxy.xml includes the wrong postgres user again.

At all: Did anybody managed to deploy pg bouncer successfully? How did you that?

Case #07798810

Best regards
Bjoern

[Mike Resseler]

Hi Bjoern,

This seems a bit weird. I'm afraid we cannot help here and you will need to continue to work with suport. I assume you restart the controller and then the proxy.xml on each proxy is being changed? Maybe there is a wrong setting from the controller propagated?

[Bjoern_ch]

I would continue working with support but for weeks there is no progress or even feedback on this! That`s why I am trying to find some help elsewhere!

[pkuikman]

In general, it is working fine. But now we have several support cases open where supports recommends to deploy pg bouncer.

So it's not running fine? PgBouncer is a lightweight connection pooler for PostgreSQL. Its main purpose is to manage and optimize database connections so your PostgreSQL server doesn’t get overwhelmed. So I guess your database has performance issues. Are you installing pg bounces standaone or on the postgres db?