Skip site navigation (1)
Skip section navigation (2)
Peripheral Links
Header And Logo
|
Site Navigation
Re: Single Index Tuple Chain (SITC) method
- From: "Zeugswetter Andreas DCP SD" <ZeugswetterA(at)spardat(dot)at>
- To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Bruce Momjian" <bruce(at)momjian(dot)us>
- Cc: "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 10:44:49 +0200
> > Here is an overview of the SITC method: > > http://momjian.us/cgi-bin/pgsitc > > A pretty fundamental problem is that the method assumes it's > OK to change the CTID of a live tuple (by swapping its item > pointer with some expired version). It is not --- this will break: I am having difficulty visualizing that. The plan is not to change CTID's (only the CTID's offset into the page is to be changed). The CTID of the new version is one that is up to now invisible to all backends, so noone can actually have remembered that CTID. Also you would first insert the slot content and then change the CTID offset (this offset change might need to be made atomic). Andreas
- References:
- Re: Single Index Tuple Chain (SITC) method
- From: Tom Lane
- Re: Single Index Tuple Chain (SITC) method
- Prev by Date: Compilatiuon of source code for windows
- Next by Date: Re: [GENERAL] UUID's as primary keys
- Previous by thread: Re: Single Index Tuple Chain (SITC) method
- Next by thread: Re: Single Index Tuple Chain (SITC) method
- Indexes: