Re: killing idle attaches without killing others
От | Gauthier, Dave |
---|---|
Тема | Re: killing idle attaches without killing others |
Дата | |
Msg-id | 482E80323A35A54498B8B70FF2B87980046602C8B1@azsmsx504.amr.corp.intel.com обсуждение исходный текст |
Ответ на | Re: killing idle attaches without killing others (Dean Rasheed <dean.a.rasheed@gmail.com>) |
Ответы |
Re: killing idle attaches without killing others
|
Список | pgsql-general |
How does PG determine if a process is <IDLE> ? It there some sort of timeout? I want to be able to distinguish betweensomene who's interrupted on the phone for a couple minutes vs the guy who left the program running over the weekend. -----Original Message----- From: pgsql-general-owner@postgresql.org [mailto:pgsql-general-owner@postgresql.org] On Behalf Of Dean Rasheed Sent: Wednesday, August 04, 2010 10:26 AM To: Vick Khera Cc: pgsql-general Subject: Re: [GENERAL] killing idle attaches without killing others On 4 August 2010 15:18, Vick Khera <vivek@khera.org> wrote: > On Wed, Aug 4, 2010 at 10:03 AM, Gauthier, Dave <dave.gauthier@intel.com> > wrote: >> >> How can one kill just the <IDLE> processes I see attached to a DB (from >> pg_stat_activity) without disturbing the others? If I need to kill the idle >> pids one ata time, which signal_name should I use for that? >> >> > > Connected to psql as a superuser, issue SELECT pg_cancel_backend(PID); where > PID is the pid of the process to close. That's a SIGINT, but it doesn't actually kill the process, it just cancels it's current query. pg_terminate_backend() sends a SIGTERM to terminate the backend. I think that function is new to 8.4, but you can still manually send the signal if you're on 8.3. http://www.postgresql.org/docs/current/static/functions-admin.html Regards, Dean -- Sent via pgsql-general mailing list (pgsql-general@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-general
В списке pgsql-general по дате отправления: