> I don’t see how to solve this problem without changing explain analyze output > to accommodate for “unknown” value. I don’t think “0” is a non-confusing > representation of “unknown” for most people, and from the practical > standpoint, a “best effort” estimate is better than 0 (i.e. I will be able to > estimate how efficient BRIN index is for my tables in terms of the number of > tuples retrieved/thrown away)
The number of retrieved and thrown away rows are already available on the upper part of the plan. Bitmap Index Scan should provide the rows that matched the index. Another alternative would be just returning the number of matching pages (by not multiplying with 10). It might be better understood. The users who can understand the EXPLAIN ANALYZE output shouldn't be expecting BRIN to return rows. -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
