Re: HOT line pointer bloat and PageRepairFragmentation

Поиск
Список
Период
Сортировка
От Pavan Deolasee
Тема Re: HOT line pointer bloat and PageRepairFragmentation
Дата
Msg-id 2e78013d0709130848x7913d6b2h97e09957f1015f4e@mail.gmail.com
обсуждение исходный текст
Ответ на Re: HOT line pointer bloat and PageRepairFragmentation  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
Ответы Re: HOT line pointer bloat and PageRepairFragmentation  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
Список pgsql-hackers


On 9/13/07, Zeugswetter Andreas ADI SD <Andreas.Zeugswetter@s-itsolutions.at> wrote:

> CREATE TABLE test (a int, b char(200));
> CREATE UNIQUE INDEX testindx ON test(a);
> INSERT INTO test VALUES (1, 'foo');
>
> Now, if we repeatedly update the tuple so that each update is a
> COLD update, we would bloat the page with redirect-dead line pointers.

Um, sorry for not understanding, but why would a COLD update produce a
redirect-dead line pointer (and not two LP_NORMAL ones) ?


The COLD updated (old) tuple would be pruned to dead line pointer
once the tuple becomes DEAD. Normally that would let us reuse the
tuple storage for other purposes. We do the same for DELETEd tuples.

Thanks,
Pavan

--
Pavan Deolasee
EnterpriseDB     http://www.enterprisedb.com

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

Предыдущее
От: "Zeugswetter Andreas ADI SD"
Дата:
Сообщение: Re: HOT line pointer bloat and PageRepairFragmentation
Следующее
От: Bruce Momjian
Дата:
Сообщение: Re: Patch queue triage