Received: from fwm1.matra-ms2i.fr (fwm1.matra-ms2i.fr [195.46.202.129]) by mail.postgresql.org (8.11.1/8.11.1) with ESMTP id f03F8x789428 for ; Wed, 3 Jan 2001 10:08:59 -0500 (EST) (envelope-from gbernard@matra-ms2i.fr) Received: by fwm1.matra-ms2i.fr; id RAA08454; Wed, 3 Jan 2001 17:11:55 +0100 (CET) Message-Id: <200101031611.RAA08454@fwm1.matra-ms2i.fr> From: "Gilles Bernard" To: "Ralf Mattes" , "Tom Lane" Cc: References: <200012290946.KAA01221@fwm1.matra-ms2i.fr> <14474.978302554@sss.pgh.pa.us> <20010101145354.A8897@forte.mh-freiburg.de> <23227.978375037@sss.pgh.pa.us> Subject: Re: Postgres ignoring RTree for geometric operators Date: Wed, 3 Jan 2001 16:09:35 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2314.1300 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300 X-Archive-Number: 200101/16 X-Sequence-Number: 150 I tryed all you suggested me : (forme && '((...))'), drop the index and recreate it and do a vacuum analyze and it still do a sequential scan on the whole table. > Ralf Mattes writes: > > Still, the remarkl about running 'vacuum' after the creation > > of an index seems valid. I was bitten by this just last week-- > > somehow it seems counterintuitive to have to vacuum a table only > > to tell the system that an index exists. This should be the job > > of 'create index' or am i wrong? > > The system knows perfectly well that the index exists. The issue > is whether the planner will conclude that the index is worth using > for a particular query, in the absence of complete statistical > information. If you've never done a 'vacuum analyze' on the table > then the planner is flying blind about what to do (and no, it does > not matter whether the index exists at the time the vacuum is done). > > There are some subtle interactions between the default estimates that > are made for various parameters. The current behavior clearly needs > work, but I'm hesitant to "fix" it by just lowering the default > selectivity estimate (or some such) without careful study. > > I'm hoping to have some time to spend on that issue for 7.2 ... > > regards, tom lane