Re: sub-select in IN clause results in sequential scan - Mailing list pgsql-performance

From Robert Haas
Subject Re: sub-select in IN clause results in sequential scan
Date
Msg-id 603c8f070910290835h10930c9dkb3e4677aeacd715b@mail.gmail.com
Whole thread Raw
In response to Re: sub-select in IN clause results in sequential scan  (Anj Adu <fotographs@gmail.com>)
Responses Re: sub-select in IN clause results in sequential scan  (Anj Adu <fotographs@gmail.com>)
List pgsql-performance
On Thu, Oct 29, 2009 at 10:10 AM, Anj Adu <fotographs@gmail.com> wrote:
> Join did not help. A sequential scan is still being done. The
> hardcoded value in the IN clause performs the best. The time
> difference is more than an order of magnitude.

If you want help debugging a performance problem, you need to post
your EXPLAIN ANALYZE results.

http://wiki.postgresql.org/wiki/Guide_to_reporting_problems

...Robert

pgsql-performance by date:

Previous
From: Ludwik Dylag
Date:
Subject: Re: database size growing continously
Next
From: Anj Adu
Date:
Subject: Re: sub-select in IN clause results in sequential scan