Received: from localhost (unknown [200.46.204.182]) by postgresql.org (Postfix) with ESMTP id 949F62E072B for ; Tue, 18 Dec 2007 00:25:39 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.182]) (amavisd-maia, port 10024) with ESMTP id 27330-05 for ; Tue, 18 Dec 2007 00:25:35 -0400 (AST) Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id A042A2E02F6 for ; Tue, 18 Dec 2007 00:25:35 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.1/8.14.1) with ESMTP id lBI4PXZs020792; Mon, 17 Dec 2007 23:25:33 -0500 (EST) To: "Tena Sakai" cc: pgsql-admin@postgresql.org Subject: Re: How would I "close" a atble? In-reply-to: References: <27986.1197936710@sss.pgh.pa.us> Comments: In-reply-to "Tena Sakai" message dated "Mon, 17 Dec 2007 19:03:44 -0800" Date: Mon, 17 Dec 2007 23:25:33 -0500 Message-ID: <20791.1197951933@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200712/159 X-Sequence-Number: 27676 "Tena Sakai" writes: > That pid 6697 caught my interest and I fished it out of "ps -ef": > postgres 6697 4916 0 Dec15 ? 00:19:45 postgres: postgres canon [local] REINDEX waiting > (and for the sake of completeness...) > postgres 12930 4916 0 11:24 ? 00:00:00 postgres: gbrush canon 172.16.1.106(37819) SELECT waiting > postgres 18177 4916 0 Dec15 ? 00:00:02 postgres: gbrush canon 172.16.1.106(53874) SELECT waiting > postgres 18825 4916 0 12:55 ? 00:00:00 postgres: tsakai canon 127.0.0.1(44558) SELECT waiting The deal here is that the REINDEX is blocked trying to get exclusive lock on table 16496, while those other guys are (apparently) stacked up behind it. What you have not shown us is what transaction has actually *got* a lock on 16496. > I could kill this process from unix > level, but before I do so, would you please comment as to why > this might have happened and what repercussion might I have > from killing it, if any? kill -INT would probably be safe enough, but you should first look into what is blocking the REINDEX from going through. regards, tom lane