| From: | MichaelDBA <MichaelDBA(at)sqlexec(dot)com> |
|---|---|
| To: | postgres performance list <pgsql-performance(at)postgresql(dot)org> |
| Cc: | Jeff Janes <jeff(dot)janes(at)gmail(dot)com>, Justin Pryzby <pryzby(at)telsasoft(dot)com>, Ivan Voras <ivoras(at)gmail(dot)com>, Andrew Gierth <andrew(at)tao11(dot)riddles(dot)org(dot)uk> |
| Subject: | Re: Optimising a two column OR check |
| Date: | 2019-10-12 15:45:45 |
| Message-ID: | 0517fa14-6a74-bcec-0655-9e240618c46f@sqlexec.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-performance |
Perhaps the fix by Alexander Kuzmenkov in V11 added this VM
consideration for having a preference of bitmap index scan over an index
only scan. Looks like I'm goin' down the rabbit hole...
Regards,
Michael Vitale
MichaelDBA wrote on 10/12/2019 11:35 AM:
> Nope, vacuumed it and still got the bitmap index scans.
>
> Andrew Gierth wrote on 10/12/2019 11:33 AM:
>>>>>>> "MichaelDBA" == MichaelDBA <MichaelDBA(at)sqlexec(dot)com> writes:
>> MichaelDBA> BTW, to Andrew, the UNION ALL alternative still results in
>> MichaelDBA> bitmap index scans from my testing.
>>
>> You probably forgot to vacuum the table.
>>
>
>
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Gierth | 2019-10-12 15:46:44 | Re: Optimising a two column OR check |
| Previous Message | MichaelDBA | 2019-10-12 15:35:22 | Re: Optimising a two column OR check |