From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Alvaro Herrera <alvherre(at)2ndquadrant(dot)com> |
Cc: | Pavan Deolasee <pavan(dot)deolasee(at)gmail(dot)com>, 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-01-26 17:27:07 |
Message-ID: | CA+TgmobLf_t-nCiZ=ECyOxbrw+sJTVXbqrxguTzBPKqB1+Rbjw@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Wed, Jan 25, 2017 at 4:08 PM, Alvaro Herrera
<alvherre(at)2ndquadrant(dot)com> wrote:
> I think the way WARM works has been pretty well hammered by now, other
> than the CREATE INDEX CONCURRENTLY issues, so I'm looking at the code
> from a maintainability point of view only.
Which senior hackers have previously reviewed it in detail?
Where would I go to get a good overview of the overall theory of operation?
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Alvaro Herrera | 2017-01-26 17:27:45 | Re: [PATCH] Rename pg_switch_xlog to pg_switch_wal |
Previous Message | Robert Haas | 2017-01-26 17:24:44 | Re: Allow interrupts on waiting standby |