Re: Issue with processes open for clients - Mailing list pgsql-admin

From Shoaib Mir
Subject Re: Issue with processes open for clients
Date
Msg-id bf54be870611100312s69fb5710pb726406808e9bb8d@mail.gmail.com
Whole thread Raw
In response to Issue with processes open for clients  ("jose fuenmayor" <jafn82@gmail.com>)
List pgsql-admin
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.

Thanks,
--------
Shoaib Mir
EnterpriseDB (www.enterprisedb.com)

On 11/10/06, jose fuenmayor < jafn82@gmail.com> wrote:
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)

Same thing using phpPgAdmin

Thanks in advance! I really aprecciate your help!

pgsql-admin by date:

Previous
From: navicat
Date:
Subject: Navicat PostgreSQL Manager for Windows finally fixed the bugs on Visual Query Builder and Backup/ Restore
Next
From: Gergely CZUCZY
Date:
Subject: schemas and tablespaces