Skip site navigation (1) Skip section navigation (2)

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

From: "Jens-Wolfhard Schicke" <j(dot)schicke(at)asco(dot)de>
To: pgsql-bugs(at)postgresql(dot)org
Subject: BUG #3225: BitmapOr plan node does not show currect row count
Date: 2007-04-13 12:31:05
Message-ID: 200704131231.l3DCV4jY096282@wwwmaster.postgresql.org (view raw or flat)
Thread:
Lists: pgsql-bugs
The following bug has been logged online:

Bug reference:      3225
Logged by:          Jens-Wolfhard Schicke
Email address:      j(dot)schicke(at)asco(dot)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.

Responses

pgsql-bugs by date

Next:From: sean songDate: 2007-04-13 14:30:49
Subject: BUG #3226: ODBC driver 8.02.02 parses subqueries incorrectly
Previous:From: Gabriele BartoliniDate: 2007-04-13 10:22:04
Subject: BUG #3224: Dump: missing schema name for sequence in a "DEFAULT nextval" specification

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group