Received: from sss.pgh.pa.us (sss.pgh.pa.us [209.114.132.154]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAONwaA66914 for ; Fri, 24 Nov 2000 18:58:36 -0500 (EST) (envelope-from tgl@sss.pgh.pa.us) Received: from sss2.sss.pgh.pa.us (tgl@localhost [127.0.0.1]) by sss.pgh.pa.us (8.11.1/8.11.1) with ESMTP id eAONwTw18198; Fri, 24 Nov 2000 18:58:29 -0500 (EST) To: "tjk@tksoft.com" cc: pgsql-sql@fc.emc.com.ph (pgsql-sql), pgsql-sql@postgresql.org Subject: Re: 7.0.3 BUG In-reply-to: <200011242351.PAA31767@uno.tksoft.com> References: <200011242351.PAA31767@uno.tksoft.com> Comments: In-reply-to "tjk@tksoft.com" message dated "Fri, 24 Nov 2000 15:51:32 -0800" Date: Fri, 24 Nov 2000 18:58:29 -0500 Message-ID: <18195.975110309@sss.pgh.pa.us> From: Tom Lane X-Archive-Number: 200011/230 X-Sequence-Number: 261 "tjk@tksoft.com" writes: > Just a wild guess, but I would imagine > a corrupt (old) index on the userid field would > cause this kind of behavior. A corrupt index might be a contributing factor, but it doesn't seem like it could be the only one. From what I know of the index routines, an entry should not be returned unless it is confirmed to pass the indexqual condition. Corrupt indexes can lead to missing output (because tuples that should match never get visited) but they shouldn't lead to outputting tuples that don't match. In any case, we don't even know whether this query used an indexscan... regards, tom lane