Re: Optimising a two column OR check

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: Optimising a two column OR check
From: Andrew Gierth <andrew@xxxxxxxxxxxxxxxxxxxx>
Date: Sat, 12 Oct 2019 16:33:37 +0100
Cc: Jeff Janes <jeff.janes@xxxxxxxxx>, Justin Pryzby <pryzby@xxxxxxxxxxxxx>, Ivan Voras <ivoras@xxxxxxxxx>, postgres performance list <pgsql-performance@xxxxxxxxxxxxxx>
In-reply-to: <a0ab3bae-6a5d-b2ea-b3a0-cbcff72f394f@sqlexec.com> (MichaelDBA@sqlexec.com's message of "Sat, 12 Oct 2019 11:27:55 -0400")
References: <CAF-QHFXQduEoX=ADZh2QYECLdcM1zOuY6=K0cE_DBjhdH3v+WA@mail.gmail.com> <20191012144336.GA4475@telsasoft.com> <CAMkU=1w1F0t7c78mJMF7DdBbk50aGy3-AROGzcbdPrS0ApmGAA@mail.gmail.com> <a0ab3bae-6a5d-b2ea-b3a0-cbcff72f394f@sqlexec.com>
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.2 (berkeley-unix)

>>>>> "MichaelDBA" == MichaelDBA  <MichaelDBA@xxxxxxxxxxx> 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.

-- 
Andrew (irc:RhodiumToad)

Follow-Ups:
- Re: Optimising a two column OR check
  - From: MichaelDBA

References:
- Optimising a two column OR check
  - From: Ivan Voras
- Re: Optimising a two column OR check
  - From: Justin Pryzby
- Re: Optimising a two column OR check
  - From: Jeff Janes
- Re: Optimising a two column OR check
  - From: MichaelDBA

Prev by Date: Re: Optimising a two column OR check
Next by Date: Re: Optimising a two column OR check
Previous by thread: Re: Optimising a two column OR check
Next by thread: Re: Optimising a two column OR check
Index(es):
- Date
- Thread

[Postgresql General] [Postgresql PHP] [PHP Users] [PHP Home] [PHP on Windows] [Kernel Newbies] [PHP Classes] [PHP Books] [PHP Databases] [Yosemite]

Powered by Linux