"Pavan Deolasee" <[EMAIL PROTECTED]> writes:

> On 5/2/07, Tom Lane <[EMAIL PROTECTED]> wrote:
>>
>> This needs a *lot* of review.  Can we break it down into more manageable
>> chunks?  
>
> Sure, we can do that. I actually did that when I posted the
> incremental versions of the HOT-patch, each version implementing
> the next big chunk of the code. I can reverse engineer that again.

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?

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.

-- 
  Gregory Stark
  EnterpriseDB          http://www.enterprisedb.com


---------------------------(end of broadcast)---------------------------
TIP 7: You can help support the PostgreSQL project by donating at

                http://www.postgresql.org/about/donate

Reply via email to