On 5/2/07, Gregory Stark <[EMAIL PROTECTED]> wrote:
Can we? I mean, sure you can break the patch up into chunks which might make it easier to read, but are any of the chunks useful alone?
Well I agree, it would be a tough job. I can try and break the patch into several self-complete incremental patches which compile and work, but I am worried about missing something somewhere and/or inserting any bugs in the process.
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. Thanks, Pavan -- EnterpriseDB http://www.enterprisedb.com
