|
|||||||||||
|
Re: [GENERAL] (Never?) Kill Postmaster?
From: Michael Harris <michael.harris(at)ericsson.com>
Date: Wed Oct 24 2007 - 03:06:38 EDT
First you need to identify the correct postgresql process. Postgresql spawns an individual server process for each database connection. They look something like this: postgres 27296 7089 9 08:00 ? 00:05:52 postgres: username databasename [local] idle If a query was running then it would say 'SELECT' instead of 'idle'. You can send a SIGINT (ie, -2) to that process to cancel a query, eg kill -2 27296 In most systems SIGINT is the default for kill so you could just do kill <pid>. The tip is ''kill -9' the postmaster', which has two important differences to the scenario I just described:
Regards // Mike
From: Stefan Schwarzer [mailto:stefan.schwarzer@grid.unep.ch]
Sent: Wednesday, 24 October 2007 3:58 PM
To: pgsql-general@postgresql.org
Hi there, I read dozens of times the "TIP 2: Don't 'kill -9' the postmaster"... Now, what am I supposed to do if I launched a query which takes ages, and which I want to interrupt? Thanks for any advice, Stef Stefan Schwarzer Lean Back and Relax - Enjoy some Nature Photography: http://photoblog.la-famille-schwarzer.de Appetite for Global Data? UNEP GEO Data Portal: Received on Wed Oct 24 03:27:35 2007 This archive was generated by hypermail 2.1.8 : Mon Jun 16 2008 - 18:46:10 EDT |
||||||||||
|
|||||||||||