Re: sub-select in IN clause results in sequential scan

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Anj Adu <fotographs(at)gmail(dot)com>
Cc: Angayarkanni <kangayarkanni(at)gmail(dot)com>, Grzegorz Jaśkiewicz <gryzman(at)gmail(dot)com>, pgsql-performance(at)postgresql(dot)org
Subject: Re: sub-select in IN clause results in sequential scan
Date: 2009-10-29 15:35:29
Message-ID: 603c8f070910290835h10930c9dkb3e4677aeacd715b@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Oct 29, 2009 at 10:10 AM, Anj Adu <fotographs(at)gmail(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Anj Adu 2009-10-29 15:40:20 Re: sub-select in IN clause results in sequential scan
Previous Message Ludwik Dylag 2009-10-29 15:33:50 Re: database size growing continously