HOT patches - Mailing list pgsql-patches

From Pavan Deolasee
Subject HOT patches
Date
Msg-id 2e78013d0705070503w681a9c9chd4a7025dd7e56edd@mail.gmail.com
Whole thread Raw
Responses Re: HOT patches
List pgsql-patches

Hi All,

Please see the set of HOT patches, broken down as suggested by
the community members for easy review. There are 5 patches, they
should apply cleanly on current CVS HEAD, but have dependencies.
So one must apply patch1 before applying patch2 and so on. At
each stage, code compiles and passes regression tests, though
things like CREATE INDEX and VACUUM may be broken until the
corresponding patches are applied. Though I've tried to decouple
the patch logically, some part of the patch may not make sense
until the later patch is reviewed. Please let me know if such things
exist.

HOT-split1.patch has the basic HOT code. It implements HOT update
if there is enough free space in the same block and none of the index
keys are changed. This should serve as a good starting point to
get the basic HOT principle without getting into any complex
optimizations.

HOT-split2.patch adds a lot of logic for further optimization such as
chain pruning, reusing LP_deleted tuples, line-pointer redirection
and row-level de-fragmentation. This patch still looks heavy, but its
difficult to split it up further. Even so, if necessary, I can try to that.

HOT-split3.patch adds some misc stuff regarding pg_stats

HOT-split4.patch fixes the VACUUM [FULL] related issues

HOT-split5.patch fixes the CREATE INDEX [CONCURRENTLY] related issue.

Please let me know if further break down is required. I would be more
than happy to provide any other support to ease the review process.

Thanks,
Pavan



--

EnterpriseDB     http://www.enterprisedb.com
Attachment

pgsql-patches by date:

Previous
From: Heikki Linnakangas
Date:
Subject: Re: Diagnostic functions
Next
From: Koichi Suzuki
Date:
Subject: Re: [HACKERS] Full page writes improvement, code update