From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at> |
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 12:42:12 |
Message-ID: | 11756.1125578532@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
"Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at> writes:
> 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).
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2005-09-01 12:50:27 | Re: On hardcoded type aliases and typmod for user types |
Previous Message | Zeugswetter Andreas DAZ SD | 2005-09-01 11:57:13 | Re: Pre-allocated free space for row |