Received: from as.tksoft.com (gyw.com [209.55.67.177] (may be forged)) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id eAONoaA66612 for ; Fri, 24 Nov 2000 18:50:36 -0500 (EST) (envelope-from tjk@tksoft.com) Received: from uno.tksoft.com (smtp3.tksoft.com [192.168.50.56] (may be forged)) by as.tksoft.com (8.8.8/8.8.8) with ESMTP id PAA12637; Fri, 24 Nov 2000 15:55:37 -0800 Received: (from tjk@tksoft.com) by uno.tksoft.com (8.8.8/8.8.8) id PAA31767; Fri, 24 Nov 2000 15:51:32 -0800 From: "tjk@tksoft.com" Message-Id: <200011242351.PAA31767@uno.tksoft.com> Subject: Re: 7.0.3 BUG To: tgl@sss.pgh.pa.us (Tom Lane) Date: Fri, 24 Nov 2000 15:51:32 -0800 (PST) Cc: pgsql-sql@fc.emc.com.ph (pgsql-sql), pgsql-sql@postgresql.org In-Reply-To: <16851.975087363@sss.pgh.pa.us> from "Tom Lane" at Nov 24, 2000 12:36:03 PM X-Mailer: ELM [version 2.5 PL2] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Archive-Number: 200011/229 X-Sequence-Number: 260 Just a wild guess, but I would imagine a corrupt (old) index on the userid field would cause this kind of behavior. You could test this by dropping the index and then rebuilding it. Troy > > "pgsql-sql" writes: > > migrate=# select userid from users where userid = 'reynan@yahoo.com'; > > userid > > --------------------- > > reynan@yahoo.com > > admin > > (2 rows) > > That's a tad, um, startling :-( > > However, you haven't given us nearly enough information to have a shot > at figuring out what's going on. > > regards, tom lane >