Postgres Pro
Downloads
Home   >   mailing lists

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

From Thomas H.
Subject Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join
Date
Msg-id 0cda01c7045b$b34f6b50$0201a8c0@iwing
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>)
Responses Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join
List pgsql-general
Tree view 
>> 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?

varchar(15) and varchar(14)

i can make them same width if that could help - just saw the same field on
the other tables are limited to 14...

regards,
thomas

pgsql-general by date:

Previous
From: Tom Lane
Date:
Subject: Re: planer picks a bad plan (seq-scan instead of index) when adding an additional join
Next
From: Cornelia Boenigk
Date:
Subject: zero values in statistic views