Re: Heap WARM Tuples - Design Draft - Mailing list pgsql-hackers

From Andres Freund
Subject Re: Heap WARM Tuples - Design Draft
Date
Msg-id 20160804163118.564ftvsck6zfgawn@alap3.anarazel.de
Whole thread Raw
In response to Heap WARM Tuples - Design Draft  (Pavan Deolasee <pavan.deolasee@gmail.com>)
Responses Re: Heap WARM Tuples - Design Draft  (Bruce Momjian <bruce@momjian.us>)
Re: Heap WARM Tuples - Design Draft  (Simon Riggs <simon@2ndquadrant.com>)
List pgsql-hackers
Hi,

On 2016-08-04 16:29:09 +0530, Pavan Deolasee wrote:
> Indexes whose values do not change do not require new index pointers. Only
> the index whose key is being changed will need a new index entry. The new
> index entry will be set to the CTID of the root line pointer.

That seems to require tracing all hot-chains in a page, to actually
figure out what the root line pointer of a warm-updated HOT tuple is,
provided it's HOT_UPDATED itself.  Or have you found a smart way to
figure that out?

Greetings,

Andres Freund



pgsql-hackers by date:

Previous
From: Simon Riggs
Date:
Subject: Re: Design for In-Core Logical Replication
Next
From: Alfred Perlstein
Date:
Subject: Re: Why we lost Uber as a user