Curious why you bothered with pgBouncer for 200 queries per day? Just future proofing?
EDIT: forgot, pgBouncer also allows you to do hitless restart/upgrade, which is useful at any query volume I suppose ;)
Indeed.
Also the server the DB is on is RAM constrained. And Postgres making a process per connection brings it right down versus using pgBouncer to pool connections.
It seems complicated but it's actually quite simple.
I've got pgBackrest set up for backups and pgBouncer for connection pooling set up so it's a case of wondering if there is some benefit to the newer versions for someone using it "casually"
Since it's require quite a bit of reconfig and testing.