| From: | Dmitry Dolgov <9erthalion6(at)gmail(dot)com> |
|---|---|
| To: | Thomas Munro <thomas(dot)munro(at)enterprisedb(dot)com> |
| Cc: | Pg Hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Causal reads take II |
| Date: | 2017-05-21 16:10:57 |
| Message-ID: | CA+q6zcXZ7Hf0Cgz4yYRPA9RA2c3K8-=OY6o5_w6yLHDrOExLTg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | 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(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`)?
> 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).
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Thomas Munro | 2017-05-21 18:32:29 | Re: Causal reads take II |
| Previous Message | Fabien COELHO | 2017-05-21 15:37:57 | Re: Variable substitution in psql backtick expansion |