Received: from mail1.rdc2.bc.home.com (mail1.rdc2.bc.home.com [24.2.10.84]) by postgresql.org (8.11.3/8.11.1) with ESMTP id f4VNK6E98043 for ; Thu, 31 May 2001 19:20:06 -0400 (EDT) (envelope-from gml1@coldresist.com) Received: from idyllic.coldresist.com ([24.113.128.171]) by mail1.rdc2.bc.home.com (InterMail vM.4.01.03.20 201-229-121-120-20010223) with ESMTP id <20010531232003.TZLA24607.mail1.rdc2.bc.home.com@idyllic.coldresist.com>; Thu, 31 May 2001 16:20:03 -0700 Message-Id: <5.1.0.14.0.20010531162518.00ae4a68@coldresist.com> X-Sender: gml1@coldresist.com X-Mailer: QUALCOMM Windows Eudora Version 5.1 Date: Thu, 31 May 2001 16:26:33 -0700 To: "Koen Antonissen" , "bernd pinter" From: Gerald Gutierrez Subject: RE: primary key scans in sequence Cc: In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; format=flowed X-Archive-Number: 200105/362 X-Sequence-Number: 3203 I think you're just witnessing the optimizer at work. If it thinks that doing sequential scans is faster, it will ignore the indices. At 11:03 AM 5/31/2001 +0200, Koen Antonissen wrote: >Thing I descovered after i posted to the group was that after creating >the scheme again, the indexes are used! after vacuum (analyze) the use >of indexes was gone again on certain tables... > >Any other suggestions?