Check pg_stat_activity for any queries that are in execution mode, where command_query will give you the query and you will also get the process ids for them in pg_stat_activity.
Hi thanks for the answer, but.... Is not when the query is executed ,is when the user cancells the query or kill the client that he is using when this query has not finished, then the process in the server is not killed still there taking resources, it happens with some clients (psql, phpPgAdmin), how can I configurate the firewall to elminate idle connections? will this eliminate all conections that are not doing anything?, because in my case the client is killed but the process in the server for that client not and continues taking resources. thanks in advance!
If you don't need the client connection after query has executed then just close that client connection or you can have it set in your firewall to kill such idle connections who are not doing anything.
Hi all , I have a question or a doubt, when I ran psql remotely it opens a process on the server, so I issue a query (select count(*) from 80millionsrowstable) then I can see that process taking cpu and mem from the server (using top), then I cancel the psql on the client, I expect to see that process gone but that is not the case it is still there! and taking resources!.
When I cancelled the query issued by the client is not supposed to eliminate the process open for him on the server?
The process stays hanging there? why is that?. Is there any parameter on postgresql or the operating system that can tune? I am using mandriva linux free 2006 kernel 2.6.12 Postgresql 8.0.8 phpPgAdmin 4.0.1 (running in a web server whit php module 5.0.4)