Re: Can Postgres use an INDEX over an OR? - Mailing list pgsql-performance

From Tom Lane
Subject Re: Can Postgres use an INDEX over an OR?
Date
Msg-id 10074.1248704308@sss.pgh.pa.us
Whole thread Raw
In response to Re: Can Postgres use an INDEX over an OR?  (Віталій Тимчишин <tivv00@gmail.com>)
Responses Re: Can Postgres use an INDEX over an OR?
List pgsql-performance
=?KOI8-U?B?96bUwcymyiD0yc3eydvJzg==?= <tivv00@gmail.com> writes:
> Actually what I am talking about is to make OR with UNION (or UNION-like
> because it's a little different depending on input rows uniqueness) as an
> option. All of OR parts can use/not use different strategies (including
> multiple different idexes or hash joins).

AFAICS you're proposing re-inventing the old implementation of OR'd
indexscans.  We took that out when we added bitmap scans because it
didn't have any performance advantage over BitmapOr.

            regards, tom lane

pgsql-performance by date:

Previous
From: Thomas Zaksek
Date:
Subject: select query performance question
Next
From: Pavel Stehule
Date:
Subject: Re: select query performance question