| From: | "Pavan Deolasee" <pavan(dot)deolasee(at)gmail(dot)com> |
|---|---|
| To: | "Zeugswetter Andreas ADI SD" <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)at> |
| Cc: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: HOT line pointer bloat and PageRepairFragmentation |
| Date: | 2007-09-13 16:56:07 |
| Message-ID: | 2e78013d0709130956t37e961fbs329567eefe072d2a@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On 9/13/07, Zeugswetter Andreas ADI SD <Andreas(dot)Zeugswetter(at)s-itsolutions(dot)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
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Alvaro Herrera | 2007-09-13 17:03:52 | Re: autovacuum launcher eating too much CPU |
| Previous Message | Zeugswetter Andreas ADI SD | 2007-09-13 16:52:48 | Re: HOT line pointer bloat and PageRepairFragmentation |