pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan Langille <dan@langille.org>
To: Ragnar Hafstaư <gnari@simnet.is>
Cc: pgsql-performance@postgresql.org
Subject: Re: index scan of whole table, can't see why
Date: Thu, 20 Jan 2005 06:56:20 -0500
Message-ID: <41EF5614.28069.CB0CC42@localhost> (raw)
In-Reply-To: <1106213669.22416.17.camel@localhost.localdomain>
References: <41EEC527.22215.A7AAF84@localhost>

On 20 Jan 2005 at 9:34, Ragnar Hafstaư wrote:

> On Wed, 2005-01-19 at 20:37 -0500, Dan Langille wrote:
> > Hi folks,
> > 
> > Running on 7.4.2, recently vacuum analysed the three tables in 
> > question.
> > 
> > The query plan in question changes dramatically when a WHERE clause 
> > changes from ports.broken to ports.deprecated.  I don't see why.  
> > Well, I do see why: a sequential scan of a 130,000 rows.  The query 
> > goes from 13ms to 1100ms because the of this.  The full plans are at 
> > http://rafb.net/paste/results/v8ccvQ54.html
> > 
> > I have tried some tuning by:
> > 
> >   set effective_cache_size to 4000, was 1000
> >   set random_page_cost to 1, was 4
> > 
> > The resulting plan changes, but no speed improvment, are at 
> > http://rafb.net/paste/results/rV8khJ18.html
> > 
> 
> this just confirms that an indexscan is not always better than a
> tablescan. by setting random_page_cost to 1, you deceiving the
> planner into thinking that the indexscan is almost as effective
> as a tablescan.
> 
> > Any suggestions please?  
> 
> did you try to increase sort_mem ?

I tried sort_mem = 4096 and then 16384. This did not make a 
difference.  See http://rafb.net/paste/results/AVDqEm55.html

Thank you.
-- 
Dan Langille : http://www.langille.org/
BSDCan - The Technical BSD Conference - http://www.bsdcan.org/




view thread (11+ messages)  latest in thread

Message-ID: <41EF5614.28069.CB0CC42@localhost>
Permalink:  ../41EF5614.28069.CB0CC42@localhost/
Also on:    postgresql.org/message-id/41EF5614.28069.CB0CC42@localhost

 · 

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 using the --to and --cc options:
  reply via email

  To: pgsql-performance@postgresql.org
  Cc: dan@langille.org, gnari@simnet.is
  Subject: Re: index scan of whole table, can't see why
  In-Reply-To: <41EF5614.28069.CB0CC42@localhost>

* 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