Re: Performance issue with NestedLoop query - Mailing list pgsql-performance

From Qingqing Zhou
Subject Re: Performance issue with NestedLoop query
Date
Msg-id CAJjS0u29U8qNqa8gWmuVeQNW-yBv=s6Q0rwv7M8z3juEipB=kw@mail.gmail.com
Whole thread Raw
In response to Performance issue with NestedLoop query  (Ram N <yramiyer@gmail.com>)
Responses Re: Performance issue with NestedLoop query
List pgsql-performance
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


pgsql-performance by date:

Previous
From: Ram N
Date:
Subject: Performance issue with NestedLoop query
Next
From: Ram N
Date:
Subject: Re: Performance issue with NestedLoop query