Received: from localhost (unknown [200.46.204.183]) by postgresql.org (Postfix) with ESMTP id 7E6EE650840 for ; Fri, 11 Jul 2008 18:39:47 -0300 (ADT) Received: from postgresql.org ([200.46.204.86]) by localhost (mx1.hub.org [200.46.204.183]) (amavisd-maia, port 10024) with ESMTP id 59126-01-7 for ; Fri, 11 Jul 2008 18:39:40 -0300 (ADT) X-Greylist: from auto-whitelisted by SQLgrey-1.7.6 Received: from silene.metacarta.com (silene.metacarta.com [208.80.142.18]) by postgresql.org (Postfix) with ESMTP id D4178650888 for ; Fri, 11 Jul 2008 18:37:49 -0300 (ADT) Received: from localhost (silene.metacarta.com [208.80.142.18]) by silene.metacarta.com (Postfix) with ESMTP id 63F0014C8097; Fri, 11 Jul 2008 17:37:47 -0400 (EDT) Received: from silene.metacarta.com ([208.80.142.18]) by localhost (silene.metacarta.com [208.80.142.18]) (amavisd-new, port 10024) with ESMTP id 05543-16; Fri, 11 Jul 2008 17:37:46 -0400 (EDT) X-Auth-Received: from [192.168.1.101] (146-115-112-146.c3-0.lex-ubr1.sbo-lex.ma.cable.rcn.com [146.115.112.146]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by silene.metacarta.com (Postfix) with ESMTP id 9FE5814C8094; Fri, 11 Jul 2008 17:37:46 -0400 (EDT) Message-ID: <4877D362.6090701@metacarta.com> Date: Fri, 11 Jul 2008 17:40:50 -0400 From: Karl Wright User-Agent: Mozilla Thunderbird 1.0.2 (Windows/20050317) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Tom Lane Cc: pgsql-performance@postgresql.org Subject: Re: REINDEX/SELECT deadlock? References: <4877918E.7030308@metacarta.com> <19251.1215805081@sss.pgh.pa.us> In-Reply-To: <19251.1215805081@sss.pgh.pa.us> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: by amavisd-new-20030616-p10 (Debian) at metacarta.com X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0 tagged_above=0 required=5 tests=none X-Spam-Level: X-Archive-Number: 200807/110 X-Sequence-Number: 30710 Tom Lane wrote: > Karl Wright writes: > >>I just noticed what looks like a deadlock situation on postgresql >>8.2.4. > > > Did you look into pg_locks to see what locks those transactions have and > are waiting for? > > regards, tom lane No. Unlike a typical transaction-based deadlock, I did not see a deadlock error come back - it just seemed to wait indefinitely instead. So I'm not even sure anything will show up in the pg_locks table. In any case, it will have to happen again before I can spelunk more, since I had to reset everything because the system was dead and it was needed by others. Karl