pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Dan Langille <dan@langille.org>
To: Stephan Szabo <sszabo@megazone.bigpanda.com>
Cc: pgsql-performance@postgresql.org
Subject: Re: index scan of whole table, can't see why
Date: Thu, 20 Jan 2005 09:40:21 -0500
Message-ID: <41EF7C85.4180.D46F54D@localhost> (raw)
In-Reply-To: <20050120061205.T35934@megazone.bigpanda.com>
References: <41EEC527.22215.A7AAF84@localhost>

On 20 Jan 2005 at 6:14, Stephan Szabo wrote:

> On Wed, 19 Jan 2005, 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
> >
> > Any suggestions please?
> 
> As a question, what does it do if enable_hashjoin is false? I'm wondering
> if it'll pick a nested loop for that step for the element/ports join and
> what it estimates the cost to be.

With enable_hashjoin = false, no speed improvement.  Execution plan 
at http://rafb.net/paste/results/qtSFVM72.html

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




view thread (11+ messages)  latest in thread

Message-ID: <41EF7C85.4180.D46F54D@localhost>
Permalink:  ../41EF7C85.4180.D46F54D@localhost/
Also on:    postgresql.org/message-id/41EF7C85.4180.D46F54D@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, sszabo@megazone.bigpanda.com
  Subject: Re: index scan of whole table, can't see why
  In-Reply-To: <41EF7C85.4180.D46F54D@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