Re: query against single partition uses index, against master table does seq scan

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mike Broers <mbroers(at)gmail(dot)com>
Cc: pgsql-performance(at)postgresql(dot)org
Subject: Re: query against single partition uses index, against master table does seq scan
Date: 2016-09-22 16:25:15
Message-ID: 27195.1474561515@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-performance

Mike Broers <mbroers(at)gmail(dot)com> writes:
> This is 9.5, sorry I didnt mention that in the initial post.

Hmm, that's odd then.

> I am guessing the issue is that the secondary non-indexed criteria is a
> search through a jsonb column?

Doubt it; it should have considered the plan you are thinking of anyway.
Maybe it did, but threw it away on some bogus cost estimate. If you could
produce a self-contained test case, I'd be willing to take a look.

regards, tom lane

In response to

Browse pgsql-performance by date

  From Date Subject
Next Message Sven R. Kunze 2016-09-23 06:35:09 Re: Multiple-Table-Spanning Joins with ORs in WHERE Clause
Previous Message Jeff Janes 2016-09-22 16:20:38 Re: Multiple-Table-Spanning Joins with ORs in WHERE Clause