pg.ddx.io  pgsql-performance@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Chris Hoover <revoohc@sermonaudio.com>
To: pgsql-performance@postgresql.org
Subject: Use of subquery causes seq scan???
Date: Tue, 20 Apr 2004 10:20:05 -0400
Message-ID: <200404201020.05699.revoohc@sermonaudio.com> (raw)
In-Reply-To: <200404151248.16067.jeremy.guthrie@berbee.com>
References: <200404151248.16067.jeremy.guthrie@berbee.com>

I need some help.  I have a query that refuses to use the provided index and 
is always sequentially scanning causing me large performance headaches.  Here 
is the basic situation:

Table A:
inv_num int
type		char
.
.
.
pkey (inv_num, type)
indx(inv_num)

Table B (has the same primary key)

Select *
from table a
where inv_num in (select inv_num from table b where ....)

Doing this causes sequential scans of both tables.  If I do a set 
enable_seqscan to false before the query, I get an index scan of table b but 
still seq scan table a. 

Is there anyway to force table a to use this index (or another) and not 
sequentially scan the table?

I'm running 7.3.4 on RedHat EL 2.1.

Thanks,

Chris




view thread (3+ messages)  latest in thread

Message-ID: <200404201020.05699.revoohc@sermonaudio.com>
Permalink:  ../200404201020.05699.revoohc@sermonaudio.com/
Also on:    postgresql.org/message-id/200404201020.05699.revoohc@sermonaudio.com

 · 

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: revoohc@sermonaudio.com
  Subject: Re: Use of subquery causes seq scan???
  In-Reply-To: <200404201020.05699.revoohc@sermonaudio.com>

* 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