Re: Understanding sequential versus index scans.

From: Greg Stark <gsstark(at)mit(dot)edu>
To: Robert James <srobertjames(at)gmail(dot)com>
Cc: Scott Marlowe <scott(dot)marlowe(at)gmail(dot)com>, Postgres General <pgsql-general(at)postgresql(dot)org>
Subject: Re: Understanding sequential versus index scans.
Date: 2009-07-20 14:13:10
Message-ID: 407d949e0907200713y6e0a081an3c3908ec1ac0e362@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

On Mon, Jul 20, 2009 at 2:22 PM, Robert James<srobertjames(at)gmail(dot)com> wrote:
> BTW, this is interesting, because there are only about 5 or 6 rows max
> returned from both queries - but I guess the planner expects more and hence
> changes the plan to remove duplicates.

If you sent the plans for the various attempts we might be able to
explain what's going on.

--
greg
http://mit.edu/~gsstark/resume.pdf

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Greg Stark 2009-07-20 14:21:54 Re: Understanding INNER JOIN versus IN subquery
Previous Message Ivan Sergio Borgonovo 2009-07-20 14:12:56 Re: Documentation Improvement suggestions