How to properly kill postgresql idle processes?

Question

PostgreSQL

Hello, I noticed on my server a lot of postgresql processes with idle status. Googling a little, I saw PGBouncer to solve this problem, set it up, launched it. But the old processes remained. Is that how it should be? The bouncer starts processing requests only after launch, but does it not touch the old ones?
Perhaps there is some other means for this, manually killing processes is not an option for me

Answer 1

pgbouncer always keeps some pool of connections running (by default, anyway, I don’t know if it can be asked to not keep connections at all for a long time). If you do not utilize them all, then they will be idle.
And it can also be old connections, if the initiator of the connection has not yet closed itself or it has not yet been closed by timeout. For example, an application may have its own connection pool.
And, of course, pgbouncer processes only those connections that are addressed specifically to it. It does not touch the DBMS at all, pgbouncer is a third-party application, for postgresql it is just another client.