pgsql: Account for the effect of lossy pages when costing bitmap scans.

From: Robert Haas <rhaas(at)postgresql(dot)org>
To: pgsql-committers(at)postgresql(dot)org
Subject: pgsql: Account for the effect of lossy pages when costing bitmap scans.
Date: 2017-11-10 21:55:35
Message-ID: E1eDHGx-0003zt-AG@gemulon.postgresql.org
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-committers

Account for the effect of lossy pages when costing bitmap scans.

Dilip Kumar, reviewed by Alexander Kumenkov, Amul Sul, and me.
Some final adjustments by me.

Discussion: http://postgr.es/m/CAFiTN-sYtqUOXQ4SpuhTv0Z9gD0si3YxZGv_PQAAMX8qbOotcg@mail.gmail.com

Branch
------
master

Details
-------
https://git.postgresql.org/pg/commitdiff/5edc63bda68a77c4d38f0cbeae1c4271f9ef4100

Modified Files
--------------
src/backend/nodes/tidbitmap.c | 37 +++++++++++++++-------
src/backend/optimizer/path/costsize.c | 59 +++++++++++++++++++++++++++++------
src/include/nodes/tidbitmap.h | 1 +
3 files changed, 75 insertions(+), 22 deletions(-)

Browse pgsql-committers by date

  From Date Subject
Next Message Andreas Seltenreich 2017-11-11 17:28:14 Re: pgsql: Remove secondary checkpoint
Previous Message Peter Eisentraut 2017-11-10 19:36:35 pgsql: Fix some null pointer dereferences in LDAP auth code