| From: | "Zeugswetter Andreas DAZ SD" <ZeugswetterA(at)spardat(dot)at> |
|---|---|
| To: | "Tom Lane" <tgl(at)sss(dot)pgh(dot)pa(dot)us>, "Hannu Krosing" <hannu(at)skype(dot)net> |
| Cc: | "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 11:57:13 |
| Message-ID: | E1539E0ED7043848906A8FF995BDA57966FB39@m0143.s-mxs.net |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> > My wild guess is that deleting all index pointers for a removed
index
> > is more-or-less the same cost as creating new ones for
> > inserted/updated page.
>
> Only if you are willing to make the removal process
> recalculate the index keys from looking at the deleted tuple.
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.
Andreas
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2005-09-01 12:42:12 | Re: Pre-allocated free space for row |
| Previous Message | Martijn van Oosterhout | 2005-09-01 10:46:58 | Re: On hardcoded type aliases and typmod for user types |