Re: Simple Join - Mailing list pgsql-performance

From Tom Lane
Subject Re: Simple Join
Date
Msg-id 7484.1134600423@sss.pgh.pa.us
Whole thread Raw
In response to Simple Join  (Kevin Brown <blargity@gmail.com>)
Responses Re: Simple Join  (Kevin Brown <blargity@gmail.com>)
Re: Simple Join  (Bruce Momjian <pgman@candle.pha.pa.us>)
Re: Simple Join  (Mitchell Skinner <mitch@arctur.us>)
List pgsql-performance
Kevin Brown <blargity@gmail.com> writes:
> I'm running 8.1 installed from source on a Debian Sarge server.  I have a
> simple query that I believe I've placed the indexes correctly for, and I
> still end up with a seq scan.  It makes sense, kinda, but it should be able
> to use the index to gather the right values.

I continue to marvel at how many people think that if it's not using an
index it must ipso facto be a bad plan ...

That plan looks perfectly fine to me.  You could try forcing some other
choices by fooling with the planner enable switches (eg set
enable_seqscan = off) but I doubt you'll find much improvement.  There
are too many rows being pulled from ordered_products to make an index
nestloop a good idea.

            regards, tom lane

pgsql-performance by date:

Previous
From: PFC
Date:
Subject: Re: Auto-tuning a VIEW?
Next
From: Kevin Brown
Date:
Subject: Re: Simple Join