Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join - Mailing list pgsql-general

From Tom Lane
Subject Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join
Date
Msg-id 12991.1163116356@sss.pgh.pa.us
Whole thread Raw
In response to planer picks a bad plan (seq-scan instead of index) when adding an additional join  ("Thomas H." <me@alternize.com>)
List pgsql-general
"Thomas H." <me@alternize.com> writes:
> SELECT * FROM shop.dvds
> LEFT JOIN oldtables.movies ON mov_id = dvd_mov_id
> LEFT JOIN shop.data_soundmedia ON sm_info_ean = dvd_ean
> WHERE (lower(mov_name) LIKE '%superman re%' OR lower(dvd_name) like
> '%superman re%' OR lower(dvd_edition) LIKE '%superman re%')

Um, what's the datatype of sm_info_ean and dvd_ean exactly?

            regards, tom lane

pgsql-general by date:

Previous
From: Alvaro Herrera
Date:
Subject: Re: autovacuum blues
Next
From: "Thomas H."
Date:
Subject: Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join