Re: Another idea for dealing with cmin/cmax

Поиск
Список
Период
Сортировка
От ITAGAKI Takahiro
Тема Re: Another idea for dealing with cmin/cmax
Дата
Msg-id 20061003124620.5F94.ITAGAKI.TAKAHIRO@oss.ntt.co.jp
обсуждение исходный текст
Ответ на Re: Another idea for dealing with cmin/cmax  (Greg Stark <gsstark@mit.edu>)
Ответы Re: Another idea for dealing with cmin/cmax  (Gregory Stark <stark@enterprisedb.com>)
Re: Another idea for dealing with cmin/cmax  ("Jonah H. Harris" <jonah.harris@gmail.com>)
Список pgsql-hackers
Greg Stark <gsstark@mit.edu> wrote:

> The plan Gavin Sherry and I were discussing at the Code Sprint was to store a
> single "most common xmin" xmin in the per-page special area. Then have a bit
> on each tuple indicating that the xmin isn't present in the tuple and instead
> to use the xmin from the page footer. Any tuples with other values of xmin
> would have to store that xmin normally.

Is this a similar approach to Interested Transaction List (ITL) in Oracle?
http://www.dbazine.com/oracle/or-articles/nanda3

ITL-like approach is more efficient than per-tuple XIDs
unless all tuples in a page are locked at the same time.
However, MAXTRANS and PCTFREE issues may bother us.

Regards,
---
ITAGAKI Takahiro
NTT Open Source Software Center




В списке pgsql-hackers по дате отправления:

Предыдущее
От: Bruce Momjian
Дата:
Сообщение: Re: [PATCHES] Bad bug in fopen() wrapper code
Следующее
От: "Magnus Hagander"
Дата:
Сообщение: Re: src/tools/msvc usage instructions