| From: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
|---|---|
| To: | Bruce Momjian <bruce(at)momjian(dot)us> |
| Cc: | Simon Riggs <simon(at)2ndquadrant(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lossy Index Tuple Enhancement (LITE) |
| Date: | 2016-08-04 17:03:34 |
| Message-ID: | CANP8+jKN4OLQ22RK6+98JkthOL5O+2fSOnCcDg8rJP5du0cJ3g@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 4 August 2016 at 02:13, Bruce Momjian <bruce(at)momjian(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2016-08-04 17:05:53 | Re: Heap WARM Tuples - Design Draft |
| Previous Message | Andres Freund | 2016-08-04 16:58:29 | Re: Heap WARM Tuples - Design Draft |