Re: HOT line pointer bloat and PageRepairFragmentation - Mailing list pgsql-hackers

From Pavan Deolasee
Subject Re: HOT line pointer bloat and PageRepairFragmentation
Date
Msg-id 2e78013d0709130956t37e961fbs329567eefe072d2a@mail.gmail.com
Whole thread Raw
In response to Re: HOT line pointer bloat and PageRepairFragmentation  ("Zeugswetter Andreas ADI SD" <Andreas.Zeugswetter@s-itsolutions.at>)
List pgsql-hackers


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

> 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.

Oh, I thought only pruned tuples from HOT chains can produce a
"redirect dead" line pointer.

This looks like a problem, since we might end up with a page filled with
LP_DEAD slots, that all have no visibility info and can thus not be
cleaned
by vacuum.


It has nothing to do with visibility info. We already know the tuple is DEAD
and thats why its line pointer is LP_DEAD.

Thanks,
Pavan

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

pgsql-hackers by date:

Previous
From: "Zeugswetter Andreas ADI SD"
Date:
Subject: Re: HOT line pointer bloat and PageRepairFragmentation
Next
From: Alvaro Herrera
Date:
Subject: Re: autovacuum launcher eating too much CPU