BUG #3225: BitmapOr plan node does not show currect row count

The following bug has been logged online:

Bug reference:      3225
Logged by:          Jens-Wolfhard Schicke
Email address:      j.schicke@asco.de
PostgreSQL version: 8.2
Operating system:   Linux
Description:        BitmapOr plan node does not show currect row count
Details:

I an explain analyze I saw recently, a BitmapOr node of 5 Bitmap Index Scan
looked like this:

BitmapOr  (cost=43.57..43.57 rows=1833 width=0) (actual time=0.146..0.146
rows=0 loops=1)

Yet, the last subnode was:

Bitmap Index Scan on location_gs  (cost=0.00..8.14 rows=251 width=0) (actual
time=0.094..0.094 rows=375 loops=1)

The real rowcount of the BitmapOr is wrong.