| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com> |
| Cc: | Tobias Florek <postgres(at)ibotty(dot)net>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>, Stephen Frost <sfrost(at)snowman(dot)net> |
| Subject: | Re: [NOVICE] WHERE clause not used when index is used |
| Date: | 2016-03-01 17:25:41 |
| Message-ID: | 16064.1456853141@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers pgsql-novice |
[ trimming -novice from the cc list ]
Jeff Janes <jeff(dot)janes(at)gmail(dot)com> writes:
> On Tue, Mar 1, 2016 at 7:40 AM, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> wrote:
>> (Problem is reproducible in 9.5 and HEAD, but not 9.4.)
> Bisects down to:
> 606c0123d627b37d5ac3f7c2c97cd715dde7842f is the first bad commit
> commit 606c0123d627b37d5ac3f7c2c97cd715dde7842f
> Author: Simon Riggs <simon(at)2ndQuadrant(dot)com>
> Date: Tue Nov 18 10:24:55 2014 +0000
> Reduce btree scan overhead for < and > strategies
Hmm ... just from the commit message, this seems much more likely to be
the cause than does the buffer locking patch Stephen fingered. Stephen,
how'd you identify 2ed5b87f as being the problem?
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2016-03-01 17:28:35 | Re: Confusing with commit time usage in logical decoding |
| Previous Message | Jeff Janes | 2016-03-01 17:22:09 | Re: [HACKERS] WHERE clause not used when index is used |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Stephen Frost | 2016-03-01 17:32:48 | Re: [NOVICE] WHERE clause not used when index is used |
| Previous Message | Jeff Janes | 2016-03-01 17:22:09 | Re: [HACKERS] WHERE clause not used when index is used |