On 1/23/26 10:14 AM, KK CHN wrote: > > > > List, > I am fronting my postgres 16 server with pgbouncer1.23.1 > > What surprises me, even though I am deploying pgbouncer as a separate > VM in front of DB server VM, the top command shows the almost same > resource usage statistics in the case of load averages, Memory usage etc > on the DB Server, whether I am infronting DB server with pgbouncer or not. > > Please find the top output from the db server pasted here. > > https://glot.io/snippets/hf4ilogbz0 <https://glot.io/snippets/hf4ilogbz0> > > My Pgbouncer server top output shows littler resource usages in terms > of CPU, MEM usage > on the top out put of pgbouncer VM ( load averagaes less than 3 > always, and Ram usage is very low, swap usage almost nil.. > > > Why eventhough I have deployed pgbouncer for this setup why DB server > still shows large resource usage as in the pasted out put.
That would seem logical to me as pgBouncer is just passing the connections to the Postgres server, the server is doing the heavy lifting of dealing with statements in the connections.
You mean to say the SQL statements are making this issue ? I also suspected wrongly formed query statements making this much load on the DB server.
I also suspect this, as the developers who write queries are not so expertised for writing optimized queries, needs to be addressed separately.
How can I find out which query statements are making the DB server on its knees ? Any method to find the bad queries? what parameters/behaviours to be checked for finding those query statements which really makes the db server to its knees by the heavy lifting ? any hints most welcome, I can explore and fix those ones.
From the top output it looks like you are working with some form of a EDB product. You need to specify what that product is and it's version.
Sorry I missed to mention it, this is an EDB 16 server. Eventhoug I prefer to use any piece of S/W that is FOSS community editions, sometimes it is demanded to manage these products too.
This list is for the community version of Postgres and people will assume that is what you are talking about. There are folks that maybe able to help with EDB versions, but they need to know what it is.
