pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Frank Wiles <frank@wiles.org>
To: Andy <frum@ar-sd.net>
Cc: pgsql-performance@postgresql.org
Subject: Re: Improving Inner Join Performance
Date: Thu, 5 Jan 2006 13:20:06 -0600
Message-ID: <20060105132006.19c7cd31.frank@wiles.org> (raw)
In-Reply-To: <001d01c6120b$0d783600$0b00a8c0@forge>
References: <001d01c6120b$0d783600$0b00a8c0@forge>

On Thu, 5 Jan 2006 17:16:47 +0200
"Andy" <frum@ar-sd.net> wrote:

> Hi to all, 
> 
> I have the following query:
> 
> SELECT count(*) FROM orders o
>       INNER JOIN report r ON r.id_order=o.id
>       WHERE o.id_status>3

> How can I improve this query's performace?? The ideea is to count all
> the values that I have in the database for the following conditions.
> If the users puts in some other search fields on the where then the
> query runs faster but in this format sometimes it takes a lot lot of
> time(sometimes even 2,3 seconds). 
> 
> Can this be tuned somehow???

  Do you have an index on report.id_order ? Try creating an index for
  it if not and run a vacuum analyze on the table to see if it gets
  rid of the sequence scan in the plan.  

 ---------------------------------
   Frank Wiles <frank@wiles.org>
   http://www.wiles.org
 ---------------------------------




view thread (10+ messages)  latest in thread

Message-ID: <20060105132006.19c7cd31.frank@wiles.org>
Permalink:  ../20060105132006.19c7cd31.frank@wiles.org/
Also on:    postgresql.org/message-id/20060105132006.19c7cd31.frank@wiles.org

 · 

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: frank@wiles.org, frum@ar-sd.net
  Subject: Re: Improving Inner Join Performance
  In-Reply-To: <20060105132006.19c7cd31.frank@wiles.org>

* 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