From: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
---|---|
To: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Causal reads take II |
Date: | 2017-05-21 18:32:29 |
Message-ID: | CAEepm=2tp_fu0GqZzN+zecfoWsD4bHL+9KHoi++mRRoPcZqVOQ@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On Mon, May 22, 2017 at 4:10 AM, Dmitry Dolgov <9erthalion6(at)gmail(dot)com> wrote:
> I'm wondering about status of this patch and how can I try it out?
Hi Dmitry, thanks for your interest.
>> On 3 January 2017 at 02:43, Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com>
>> wrote:
>> The replay lag tracking patch this depends on is in the current commitfest
>
> I assume you're talking about this patch [1] (at least it's the only thread
> where I could find a `replay-lag-v16.patch`)? But `replay lag tracking` was
> returned with feedback, so what's the status of this one (`causal reads`)?
Right, replay lag tracking was committed. I'll post a rebased causal
reads patch later today.
--
Thomas Munro
http://www.enterprisedb.com
From | Date | Subject | |
---|---|---|---|
Next Message | Thomas Munro | 2017-05-21 18:39:35 | Re: WIP: [[Parallel] Shared] Hash |
Previous Message | Dmitry Dolgov | 2017-05-21 16:10:57 | Re: Causal reads take II |