"Mikael Carneholm" <Mikael.Carneholm@WirelessCar.com> writes:
> ..and this last AND seems unnessecary, since the predicate on
> (driver_activity_type__id = 5) is included in each of the above
> conditions.
This should be fixed by the changes I made recently in choose_bitmap_and
--- it wasn't being aggressive about pruning overlapping AND conditions
when a sub-OR was involved. It's possible the new coding is *too*
aggressive, and will reject indexes that it'd be profitable to include;
but at least it won't make this particular mistake.
regards, tom lane
