Re: Proposal: Improve bitmap costing for lossy pages
Robert Haas <robertmhaas@gmail.com>
From: Robert Haas <robertmhaas@gmail.com>
To: Dilip Kumar <dilipbalaut@gmail.com>
Cc: pgsql-hackers <pgsql-hackers@postgresql.org>
Date: 2017-08-18T03:26:14Z
Lists: pgsql-hackers
On Thu, Aug 17, 2017 at 12:06 AM, Dilip Kumar <dilipbalaut@gmail.com> wrote: > I have attempted a very simple POC with this approach just to see how > many lossy pages we can save if we lossify all the pages falling in > the same chunk first, before moving to the next page. I have taken > some data on TPCH scale 20 with different work_mem (only calculated > lossy pages did not test performance). I did not see a significant > reduction in lossy pages. (POC patch attached with the mail in case > someone is interested to test or more experiment). That's not an impressive savings. Maybe this approach is a dud, and we should go back to just tackling the planner end of it. -- Robert Haas EnterpriseDB: http://www.enterprisedb.com The Enterprise PostgreSQL Company
Commits
-
Account for the effect of lossy pages when costing bitmap scans.
- 5edc63bda68a 11.0 landed