pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Gilles Bernard <gbernard@matra-ms2i.fr>
To: Ralf Mattes <rm@mh-freiburg.de>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: pgsql-docs@postgresql.org
Subject: Re: Postgres ignoring RTree for geometric operators
Date: Wed, 3 Jan 2001 16:09:35 +0100
Message-ID: <200101031611.RAA08454@fwm1.matra-ms2i.fr> (raw)
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>

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 <rm@mh-freiburg.de> 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




view thread (7+ messages)  latest in thread

Message-ID: <200101031611.RAA08454@fwm1.matra-ms2i.fr>
Permalink:  ../200101031611.RAA08454@fwm1.matra-ms2i.fr/
Also on:    postgresql.org/message-id/200101031611.RAA08454@fwm1.matra-ms2i.fr

 · 

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients from your mail client; the link fills in
  the headers below: reply via email
  Some clients, webmail especially, drop In-Reply-To and References from
  a link, and the reply then starts a new thread: use the mbox below.

  To: pgsql-docs@postgresql.org
  Cc: gbernard@matra-ms2i.fr, rm@mh-freiburg.de, tgl@sss.pgh.pa.us
  Subject: Re: Postgres ignoring RTree for geometric operators
  In-Reply-To: <200101031611.RAA08454@fwm1.matra-ms2i.fr>
  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> <200101031611.RAA08454@fwm1.matra-ms2i.fr>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox