Re: Performance issue with NestedLoop query

On Thu, Jul 30, 2015 at 12:51 AM, Ram N <yramiyer@gmail.com> wrote:
> "              ->  Index Scan using end_date_idx on public.table2 b
> (cost=0.43..23181.37 rows=345833 width=52) (actual time=0.063..622.274
> rows=403936 loops=181)"
> "                    Output: b.serial_no, b.name, b.st, b.end_date, b.a,
> b.start_date"
> "                    Index Cond: (a.ts < b.end_date)"
> "                    Filter: (a.ts > b.start_date)"
> "                    Rows Removed by Filter: 392642"

In your case, do you have index built for both b.end_date and
b.start_date? If so, can you try

set enable_index=off

to see if bitmap heap scan helps?

Regards,
Qingqing