On Mon, Sep 5, 2016 at 1:53 PM, Pavan Deolasee <pavan.deola...@gmail.com> wrote: > 0001_track_root_lp_v4.patch: This patch uses a free t_infomask2 bit to track > latest tuple in an update chain. The t_ctid.ip_posid is used to track the > root line pointer of the update chain. We do this only in the latest tuple > in the chain because most often that tuple will be updated and we need to > quickly find the root only during update. > > 0002_warm_updates_v4.patch: This patch implements the core of WARM logic. > During WARM update, we only insert new entries in the indexes whose key has > changed. But instead of indexing the real TID of the new tuple, we index the > root line pointer and then use additional recheck logic to ensure only > correct tuples are returned from such potentially broken HOT chains. Each > index AM must implement a amrecheck method to support WARM. The patch > currently implements this for hash and btree indexes.
Moved to next CF, I was surprised to see that it is not *that* large: 43 files changed, 1539 insertions(+), 199 deletions(-) -- Michael -- Sent via pgsql-hackers mailing list (firstname.lastname@example.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers