Re: vacuum, performance, and MVCC
От | Mark Woodward |
---|---|
Тема | Re: vacuum, performance, and MVCC |
Дата | |
Msg-id | 18564.24.91.171.78.1151151250.squirrel@mail.mohawksoft.com обсуждение исходный текст |
Ответ на | Re: vacuum, performance, and MVCC (Jan Wieck <JanWieck@Yahoo.com>) |
Ответы |
Re: vacuum, performance, and MVCC
Re: vacuum, performance, and MVCC |
Список | pgsql-hackers |
> On 6/23/2006 3:10 PM, Mark Woodward wrote: > >> This is NOT an "in-place" update. The whole MVCC strategy of keeping old >> versions around doesn't change. The only thing that does change is one >> level of indirection. Rather than keep references to all versions of all >> rows in indexes, keep only a reference to the first or "key" row of each >> row, and have the first version of a row form the head of a linked list >> to >> subsequent versions of each row. The list will be in decending order. > > Where exactly do you intend to keep all those links (for a table with N > indexes)? > I'm probably mistaken, but aren't there already forward references in tuples to later versions? If so, I'm only sugesting reversing the order and referencing the latest version.
В списке pgsql-hackers по дате отправления: