Re: Pre-allocated free space for row

From: "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at>
To: "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Cc: "Hannu Krosing" <hannu(at)skype(dot)net>, "Satoshi Nagayasu" <nagayasus(at)nttdata(dot)co(dot)jp>, "Simon Riggs" <simon(at)2ndquadrant(dot)com>, <josh(at)agliodbs(dot)com>, <pgsql-hackers(at)postgresql(dot)org>, "Jim C(dot) Nasby" <jnasby(at)pervasive(dot)com>
Subject: Re: Pre-allocated free space for row
Date: 2005-09-01 13:26:25
Message-ID: E1539E0ED7043848906A8FF995BDA57966FB84@m0143.s-mxs.net
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers


> > The bgwriter could "update" all columns of dead heap tuples in heap
> > pages to NULL and thus also gain free space without the need to
touch
> > the indexes.
> > The slot would stay used but it would need less space.
>
> Not unless it's running a transaction (consider TOAST updates).

Ok, you could leave all toast pointers and the toast table as is.

Andreas

Browse pgsql-hackers by date

  From Date Subject
Next Message Andrew - Supernews 2005-09-01 13:29:17 Re: TODO item: set proper permissions on non-system schemas
Previous Message Tom Lane 2005-09-01 13:22:35 Re: Remove xmin and cmin from frozen tuples