Skip site navigation (1) Skip section navigation (2)

Re: Patch: Write Amplification Reduction Method (WARM)

From: Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>
To: Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>
Cc: Haribabu Kommi <kommi(dot)haribabu(at)gmail(dot)com>, Tomas Vondra <tomas(dot)vondra(at)2ndquadrant(dot)com>, pgsql-hackers <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Patch: Write Amplification Reduction Method (WARM)
Date: 2017-01-03 04:13:38
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Tue, Dec 27, 2016 at 6:51 PM, Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>

> Thanks Jaime for the tests and bug reports. I'm attaching an add-on patch
> which fixes these issues for me. I'm deliberately not sending a fresh
> revision because the changes are still minor.

Per Alvaro's request in another thread, I've rebased these patches on his
patch to refactor HeapSatisfiesHOTandKeyUpdate(). I've also attached that
patch here for easy reference.

The fixes based on bug reports by Jaime are also included in this patch
set. Other than that there are not any significant changes. The patch still
disables WARM on system tables, something I would like to fix. But I've
been delaying that because it will require changes at several places since
indexes on system tables are managed separately. In addition to that, the
patch only works with btree and hash indexes. We must implement the recheck
method for other index types so as to support them.


 Pavan Deolasee         
 PostgreSQL Development, 24x7 Support, Training & Services

Attachment: interesting-attrs-2.patch
Description: application/octet-stream (11.7 KB)
Attachment: 0001_track_root_lp_v7.patch
Description: application/octet-stream (27.4 KB)
Attachment: 0002_warm_updates_v7.patch
Description: application/octet-stream (103.7 KB)

In response to


pgsql-hackers by date

Next:From: Craig RingerDate: 2017-01-03 04:36:27
Subject: Re: [PATCH] enhancements, pg_lsn helper, and some more recovery tests
Previous:From: Tom LaneDate: 2017-01-03 03:47:28
Subject: Re: Odd behavior with PG_TRY

Privacy Policy | About PostgreSQL
Copyright © 1996-2018 The PostgreSQL Global Development Group