On Fri, Aug 5, 2016 at 09:40:35PM -0400, Bruce Momjian wrote:
> So to summarize again:
>
> o chains start out as HOT
> o they become WARM when some indexes change and others don't
> o for multiple index changes, we have to check all indexes
> for key/ctid matches
> o for single index changes, we can fail HOT and create a new
> non-HOT/WARM tuple if there are too many index matches
> o 99% of index checks will not find a key/ctid match
I think a WARM chain where the the head ctid isn't LP_REDIRECT wasn't
pruned, so here is an updated list:
o chains start out as HOT
o they become WARM when some indexes change and others don't
o if WARM chain head is not LP_REDIRECT, check existing chain for key
matches
o if WARM chain head is LP_REDIRECT:
o for single index changes, we can fail HOT and create a new
non-HOT/WARM tuple if there are too many index matches
o for multiple index changes, we have to check all indexes
for key/ctid matches
o 99% of index checks will not find a key/ctid match
So, we are only checking the index if the WARM chain was pruned, and we
can bail out if there is only one index changed. This is looking more
doable.
--
Bruce Momjian <br...@momjian.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 +
--
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers
