pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Scott Cain <cain@cshl.org>
To: Rod Taylor <rbt@rbt.ca>
Cc: Postgresql Performance <pgsql-performance@postgresql.org>
Subject: Re: force the use of a particular index
Date: 11 Jul 2003 14:23:04 -0400
Message-ID: <1057947784.5767.39.camel@localhost.localdomain> (raw)
In-Reply-To: <1057947284.65544.129.camel@jester>
References: <1057850280.1451.22.camel@localhost.localdomain>
	<1057920672.46100.149.camel@jester>
	<1057929459.5766.7.camel@localhost.localdomain>
	<1057930695.46100.172.camel@jester>
	<1057937779.5767.17.camel@localhost.localdomain>
	<1057940450.65544.14.camel@jester>
	<1057944059.5766.34.camel@localhost.localdomain>
	<1057947284.65544.129.camel@jester>

On Fri, 2003-07-11 at 14:14, Rod Taylor wrote:
> > > set enable_hashjoin = false;
> > 
> > BINGO!
> 
> I'm not so sure about that.  Your dataset seems to have changed fairly
> significantly since the last test.
> 
> > ->  Index Scan using feature_pkey on feature f  (cost=0.00..134592.43 rows=47912 width=39) (actual time=0.46..502.50 rows=431 loops=1)
> 
> Notice it only pulled out 431 rows where prior runs pulled out several
> thousand (~13000).  I think what really happened was something came
> along and deleted a bunch of stuff, then vacuum ran.

There is nearly a zero chance that happened.  This database is
accessible only by me, I haven't deleted anything.  The only things I
have done is to create and drop various indexes and run vacuum.  Is
there anything else that could explain the difference?  Is the index
scan on feature_pkey using information from the index scan on
featureloc_src_6 to limit the number of rows to get from feature?

Scott

-- 
------------------------------------------------------------------------
Scott Cain, Ph. D.                                         cain@cshl.org
GMOD Coordinator (http://www.gmod.org/)                     216-392-3087
Cold Spring Harbor Laboratory




view thread (12+ messages)

Message-ID: <1057947784.5767.39.camel@localhost.localdomain>
Permalink:  ../1057947784.5767.39.camel@localhost.localdomain/
Also on:    postgresql.org/message-id/1057947784.5767.39.camel@localhost.localdomain

 · 

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-performance@postgresql.org
  Cc: cain@cshl.org, rbt@rbt.ca
  Subject: Re: force the use of a particular index
  In-Reply-To: <1057947784.5767.39.camel@localhost.localdomain>
  References: <1057850280.1451.22.camel@localhost.localdomain> <1057920672.46100.149.camel@jester> <1057929459.5766.7.camel@localhost.localdomain> <1057930695.46100.172.camel@jester> <1057937779.5767.17.camel@localhost.localdomain> <1057940450.65544.14.camel@jester> <1057944059.5766.34.camel@localhost.localdomain> <1057947284.65544.129.camel@jester> <1057947784.5767.39.camel@localhost.localdomain>

* 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