Re: Lossy Index Tuple Enhancement (LITE) - Mailing list pgsql-hackers

From Simon Riggs
Subject Re: Lossy Index Tuple Enhancement (LITE)
Date
Msg-id CANP8+jKN4OLQ22RK6+98JkthOL5O+2fSOnCcDg8rJP5du0cJ3g@mail.gmail.com
Whole thread Raw
In response to Re: Lossy Index Tuple Enhancement (LITE)  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Lossy Index Tuple Enhancement (LITE)  (Bruce Momjian <bruce@momjian.us>)
List pgsql-hackers
On 4 August 2016 at 02:13, Bruce Momjian <bruce@momjian.us> wrote:

> How do plan to clear the bitmask so it, over time, doesn't end up being
> all-set?

I don't have a plan, though thoughts welcome.

Similar situation that our current indexes don't recover from bloat, a
situation made worse by non-HOT updates.

So, we have a choice of which disadvantage to accept.


> Also, why not use this bitmap for all indexes, not just update chains?

I don't understand where you get this update chains thing from.

The bitmap can apply to multiple tuples on one page, which is described.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Andres Freund
Date:
Subject: Re: Heap WARM Tuples - Design Draft
Next
From: Bruce Momjian
Date:
Subject: Re: Heap WARM Tuples - Design Draft