> > 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
(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
so noone can actually have remembered that CTID.
Also you would first insert the slot content and then change the CTID
(this offset change might need to be made atomic).
In response to
pgsql-hackers by date
|Next:||From: Martijn van Oosterhout||Date: 2006-06-29 09:33:13|
|Subject: Re: [GENERAL] UUID's as primary keys|
|Previous:||From: Simon Riggs||Date: 2006-06-29 08:39:27|
|Subject: Re: [HACKERS] Non-transactional pg_class, try 2|