Re: Heap WARM Tuples - Design Draft

From: Bruce Momjian <bruce(at)momjian(dot)us>
To: Claudio Freire <klaussfreire(at)gmail(dot)com>
Cc: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Heap WARM Tuples - Design Draft
Date: 2016-08-05 15:45:16
Message-ID: 20160805154516.GD5068@momjian.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Fri, Aug 5, 2016 at 12:25:39PM -0300, Claudio Freire wrote:
> > 2. The existence of index pointers to intermediate tuples will lead to index
> > bloat. This is the same problem that we found in Simon's original proposal
> > (discussed internally). None of the intermediate line pointers can be
> > vacuumed until the entire chain becomes DEAD. Event if the a duplicate index
> > key is inserted for every index, knowing that and reclaiming to the index
> > pointers to the original root line pointer, will be difficult.
>
> I don't see the difference it makes for bloat between storing the root
> tid and the intermediate tid, but I haven't yet figured out how
> vacuuming would work so maybe I have to think about that to realize
> the difference.

Think of page pruning --- we can't remove a ctid that an index points
to. The more ctids you point to in a HOT chain, the fewer ctids you can
remove --- that's why we want to point only to the head of the HOT/WARM
chain.

--
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 +

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Robert Haas 2016-08-05 15:50:25 Re: regression test for extended query protocol
Previous Message Claudio Freire 2016-08-05 15:25:39 Re: Heap WARM Tuples - Design Draft