Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Single Index Tuple Chain (SITC) method
- From: Bruce Momjian <bruce(at)momjian(dot)us>
- To: Martijn van Oosterhout <kleptog(at)svana(dot)org>
- Cc: Hannu Krosing <hannu(at)skype(dot)net>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>, Greg Stark <gsstark(at)mit(dot)edu>, PFC <lists(at)peufeu(dot)com>
- Subject: Re: Single Index Tuple Chain (SITC) method
- Date: Thu, 29 Jun 2006 14:54:01 -0400 (EDT)
Martijn van Oosterhout wrote: > One thing I am confused about, currently the ctid chain follows tuple > history so that transactions can find the latest version of any tuple, > even if the key fields have changed. This proposal breaks that, I'm not > sure how important that is though. No, SITC doesn't break the UPDATE chain, it merely doesn't set the SITC_NOT_TAIL bit on the tuple, so an index scan knows that is the last tuple for that index entry. -- Bruce Momjian bruce(at)momjian(dot)us EnterpriseDB http://www.enterprisedb.com + If your life is a hard drive, Christ can be your backup. +
- References:
- Re: Single Index Tuple Chain (SITC) method
- From: Martijn van Oosterhout
- Re: Single Index Tuple Chain (SITC) method
- Prev by Date: Re: Single Index Tuple Chain (SITC) method
- Next by Date: Re: Single Index Tuple Chain (SITC) method
- Previous by thread: Re: Single Index Tuple Chain (SITC) method
- Next by thread: Re: [GENERAL] UUID's as primary keys
- Indexes: