On Mon, May 22, 2017 at 6:32 AM, Thomas Munro <thomas.mu...@enterprisedb.com> wrote: > On Mon, May 22, 2017 at 4:10 AM, Dmitry Dolgov <9erthali...@gmail.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.mu...@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`)? > > Right, replay lag tracking was committed. I'll post a rebased causal > reads patch later today.
I ran into a problem while doing this, and it may take a couple more days to fix it since I am at pgcon this week. More soon. -- Thomas Munro http://www.enterprisedb.com -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
