| From: | Bruce Momjian <bruce(at)momjian(dot)us> |
|---|---|
| To: | Simon Riggs <simon(at)2ndquadrant(dot)com> |
| Cc: | PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Lossy Index Tuple Enhancement (LITE) |
| Date: | 2016-08-04 00:34:02 |
| Message-ID: | 20160804003402.GE1702@momjian.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Thu, Aug 4, 2016 at 01:16:20AM +0100, Simon Riggs wrote:
> > Would you only add a LITE index entry when there isn't an
> > existing index entry for the same values and heap page? That seems
> > quite complicated.
>
> The insertion algorithm is described. Doesn't seem complicated to me.
Ah, I see it now:
As UPDATEs occur we request inserts into the index. If a lossy index
pointer already exists that covers the new linepointer then we skip
the index insert, optimizing writes to the index.
I thought you meant "already exists" just means it matches the existing
range. I was unclear that was the entire page.
--
Bruce Momjian <bruce(at)momjian(dot)us> http://momjian.us
EnterpriseDB http://enterprisedb.com
+ As you are, so once was I. As I am, so you will be. +
+ Ancient Roman grave inscription +
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Michael Paquier | 2016-08-04 00:37:02 | Re: Way to access LSN (for each transaction) by directly talking to postgres? |
| Previous Message | Bruce Momjian | 2016-08-04 00:32:57 | Re: Lossy Index Tuple Enhancement (LITE) |