Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages - Mailing list pgsql-hackers

From Robert Haas
Subject Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages
Date
Msg-id CA+Tgmoa3b-sXMVXDQBqn+3G8VK4yCmteb6CVcOBDSsFBJXKvew@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Proposal: Improve bitmap costing for lossy pages  (Dilip Kumar <dilipbalaut@gmail.com>)
List 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



pgsql-hackers by date:

Previous
From: Robert Haas
Date:
Subject: Re: [HACKERS] Hash Functions
Next
From: Amit Langote
Date:
Subject: Re: [HACKERS] expanding inheritance in partition bound order