Re: PG choosing nested loop for set membership? - Mailing list pgsql-general

From Brian Crowell
Subject Re: PG choosing nested loop for set membership?
Date
Msg-id CAAQkdDoaUB5JfN4SgKqWbhwXGXeb6BmaQxLNibXAYxnbgtwe_Q@mail.gmail.com
Whole thread Raw
In response to Re: PG choosing nested loop for set membership?  (David Johnston <polobo@yahoo.com>)
List pgsql-general
On Tue, Mar 25, 2014 at 4:12 PM, David Johnston <polobo@yahoo.com> wrote:
> 2 - and the one I'd use by default) Use an INNER JOIN

That's where I started, but Postgres is smart enough to know that this
is equivalent to what I'm doing, and still picks the nested loop. I
went to IN in the hopes of tricking it.

I haven't tried EXISTS. I'll have to try that tomorrow.

--Brian


pgsql-general by date:

Previous
From: Brian Crowell
Date:
Subject: Re: PG choosing nested loop for set membership?
Next
From: John Smith
Date:
Subject: Re: tsearch2: how to plainto_tsquery() with "|"