Re: Performance issue with NestedLoop query

From: Qingqing Zhou <zhouqq(dot)postgres(at)gmail(dot)com>
To: Ram N <yramiyer(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: Performance issue with NestedLoop query
Date: 2015-07-30 20:24:51
Message-ID: CAJjS0u29U8qNqa8gWmuVeQNW-yBv=s6Q0rwv7M8z3juEipB=kw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

On Thu, Jul 30, 2015 at 12:51 AM, Ram N <yramiyer(at)gmail(dot)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

In response to

Responses

Browse pgsql-performance by date

  From Date Subject
Next Message Ram N 2015-07-31 17:55:44 Re: Performance issue with NestedLoop query
Previous Message Ram N 2015-07-30 07:51:44 Performance issue with NestedLoop query