Joshua D. Drake wrote:
> Pavan Deolasee wrote:
>>
>> I suppose inserting HOT tuples without index maintenance is useful
>> even if no
>> changes to the space allocation is made is useful. It won't get the
>> space
>> usage but it would save on index thrashing. But that still implies
>> all the
>> code to handle scans, updates, index builds, etc. Those chunks
>> could be
>> separated out but you can't commit without them.
>>
>> There are few things that we can separate easily, like CREATE INDEX
>> related changes, VACUUM and VACUUM FULL related changed, space
>> reuse related changes etc. Let me give it a shot.
>
> Did we ever get a broken up patch for this?
Yes:
http://archives.postgresql.org/pgsql-patches/2007-05/msg00065.php
-- Heikki Linnakangas EnterpriseDB http://www.enterprisedb.com
