Re: [HACKERS] Causal reads take II - Mailing list pgsql-hackers

From Dmitry Dolgov
Subject Re: [HACKERS] Causal reads take II
Date
Msg-id CA+q6zcXZ7Hf0Cgz4yYRPA9RA2c3K8-=OY6o5_w6yLHDrOExLTg@mail.gmail.com
Whole thread Raw
In response to [HACKERS] Causal reads take II  (Thomas Munro <thomas.munro@enterprisedb.com>)
Responses Re: [HACKERS] Causal reads take II  (Thomas Munro <thomas.munro@enterprisedb.com>)
List pgsql-hackers
Hi

I'm wondering about status of this patch and how can I try it out?

> On 3 January 2017 at 02:43, Thomas Munro <thomas.munro@enterprisedb.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`)?

> First apply replay-lag-v16.patch, then refactor-syncrep-exit-v16.patch, then
> causal-reads-v16.patch.

It would be nice to have all three of them attached (for some reason I see only
last two of them in this thread). But anyway there are a lot of failed hunks
when I'm trying to apply `replay-lag-v16.patch` and `refactor-syncrep-exit-v16.patch`,
`causal-reads-v16.patch` (or last two of them separately).

pgsql-hackers by date:

Previous
From: Fabien COELHO
Date:
Subject: Re: [HACKERS] Variable substitution in psql backtick expansion
Next
From: Thomas Munro
Date:
Subject: Re: [HACKERS] Causal reads take II