This is a discussion on kill off idle connections? within the Pgsql Performance forums, part of the PostgreSQL category; --> Hi. Is there any way to kill idle connections using up memory on the server? A part of workload ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| Hi. Is there any way to kill idle connections using up memory on the server? A part of workload on the server are users connecting randomly to a web application, querying very large reports, saving them and then closing the webapp. Reports use a lot of memory and we have set the work_mem to 256Mb on a 4Gb RAM server. However the problem is, over time idle connections that use a lot of ram accumulate and I see a new user connecting (via stat news) and issuing a query with rather awful performance, supposedly because it goes to swap and he is not using those idle "pooled" connections. I have checked that php application is closing connections just in case, and it does. It;s something between pgsql and apache, when yoiu restart apache the pool is reset and idle connections disappear. Is there any way to kill them off manually? |
| ||||
| Hi. Can someone please help me with that? We added a couple more applications to the same database and now there are 25+ connections sitting there eating memory any given moment, all of them idle with new clients generating more connections and memory full all the time? How do I kill them off? Should I post to .general instead, I was told I should go to .performance with performance related issues. |