This is a discussion on Re: Pre-allocated free space for row within the pgsql Hackers forums, part of the PostgreSQL category; --> > > My wild guess is that deleting all index pointers for a removed index > > is more-or-less ...
| |||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
| ||||
| > > 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 ---------------------------(end of broadcast)--------------------------- TIP 4: Have you searched our list archives? http://archives.postgresql.org |
| ||||
| "Zeugswetter Andreas DAZ SD" <ZeugswetterA@spardat.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 ---------------------------(end of broadcast)--------------------------- TIP 1: if posting/reading through Usenet, please send an appropriate subscribe-nomail command to majordomo@postgresql.org so that your message can get through to the mailing list cleanly |