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: Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>
Cc: Jaime Casanova <jaime(dot)casanova(at)2ndquadrant(dot)com>, 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-02-02 12:47:46
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-hackers
On Wed, Feb 1, 2017 at 3:21 AM, Alvaro Herrera <alvherre(at)2ndquadrant(dot)com>

> Alvaro Herrera wrote:
> > Unless there are objections I will push this later this afternoon.
> Done.  Let's get on with the show -- please post a rebased WARM.
Please see rebased patches attached. There is not much change other than
the fact the patch now uses new catalog maintenance API.

Do you think we should apply the patch to remove ItemPointerCopy()? I will
rework the HeapTupleHeaderGetNextTid() after that. Not that it depends on
removing ItemPointerCopy(), but decided to postpone it until we make a call
on that patch.

BTW I've run now long stress tests with the patch applied and see no new
issues, even when indexes are dropped and recreated concurrently (includes
my patch to fix CIC bug in the master though). In another 24 hour test,
WARM could do 274M transactions where as master did 164M transactions. I
did not drop and recreate indexes during this run.


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

Attachment: 0002_warm_updates_v11.patch
Description: application/octet-stream (120.8 KB)
Attachment: 0001_track_root_lp_v11.patch
Description: application/octet-stream (38.4 KB)
Attachment: 0000_interesting_attrs.patch
Description: application/octet-stream (11.4 KB)

In response to


pgsql-hackers by date

Next:From: Magnus HaganderDate: 2017-02-02 13:13:46
Subject: Re: Enabling replication connections by default in pg_hba.conf
Previous:From: Amit KapilaDate: 2017-02-02 12:44:57
Subject: Re: Index corruption with CREATE INDEX CONCURRENTLY

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