Received: from localhost (pluto.hub.org [200.46.204.4]) by postgresql.org (Postfix) with ESMTP id 1F88B9FA4AD for ; Fri, 3 Nov 2006 02:23:45 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.4]) (amavisd-new, port 10024) with ESMTP id 35065-01 for ; Fri, 3 Nov 2006 02:23:42 -0400 (AST) X-Greylist: from auto-whitelisted by SQLgrey- Received: from sss.pgh.pa.us (sss.pgh.pa.us [66.207.139.130]) by postgresql.org (Postfix) with ESMTP id 7BA9B9FA217 for ; Fri, 3 Nov 2006 02:23:42 -0400 (AST) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.13.6/8.13.6) with ESMTP id kA36NSBl026797; Fri, 3 Nov 2006 01:23:28 -0500 (EST) To: Jeff Frost cc: pgsql-sql@postgresql.org Subject: Re: delete and select with IN clause issues In-reply-to: References: <24512.1162525800@sss.pgh.pa.us> Comments: In-reply-to Jeff Frost message dated "Thu, 02 Nov 2006 20:37:00 -0800" Date: Fri, 03 Nov 2006 01:23:28 -0500 Message-ID: <26796.1162535008@sss.pgh.pa.us> From: Tom Lane X-Virus-Scanned: Maia Mailguard 1.0.1 X-Archive-Number: 200611/32 X-Sequence-Number: 26684 Jeff Frost writes: > On Thu, 2 Nov 2006, Tom Lane wrote: >> This seems pretty darn weird. I am wondering about corrupt indexes --- >> can you find the indicated key in either table if you set >> enable_indexscan and enable_bitmapscan to 0? > test_tracking=# begin; > BEGIN > test_tracking=# set enable_seqscan TO false; > SET > test_tracking=# set enable_bitmapscan to false; > SET That's not actually the test case I asked for ... > Nope, I guess I didn't \d visit..thought I did...it's below. I'm going to > guess that there is index corruption and a reindex page_view will fix it. Do > you want me to gather any information in case this is a reproducible bug > before I issue the reindex? I'm thinking the same --- please save a physical copy of page_view_visit_idx before you reindex it, and if that fixes the problem, please send me copies of both the before and after states of the index. regards, tom lane