Re: [HACKERS] make async slave to wait for lsn to be replayed
David Steele <david@pgmasters.net>
From: David Steele <david@pgmasters.net>
To: Fujii Masao <masao.fujii@gmail.com>,
Ivan Kartyshov <i.kartyshov@postgrespro.ru>
Cc: Michael Paquier <michael@paquier.xyz>,
PostgreSQL-development <pgsql-hackers@postgresql.org>
Date: 2020-03-04T12:17:31Z
Lists: pgsql-hackers
On 3/4/20 5:36 AM, Fujii Masao wrote: > On Tue, Mar 13, 2018 at 10:06 PM David Steele <david@pgmasters.net> wrote: >> On 3/6/18 9:25 PM, Michael Paquier wrote: >>> On Tue, Mar 06, 2018 at 02:24:24PM +0300, Ivan Kartyshov wrote: >>>> Hello, I now is preparing the patch over syntax that Simon offered. And in >>>> few day I will update the patch. >>>> Thank you for your interest in thread. >>> >>> It has been more than one month since a patch update has been requested, >>> and time is growing short. This refactored patch introduces a whole new >>> concept as well, so my recommendation would be to mark this patch as >>> returned with feedback, and then review it freshly for v12 if this >>> concept is still alive and around. >> >> This patch wasn't updated at the beginning of the CF and still hasn't >> been updated after almost two weeks. >> >> I have marked the patch Returned with Feedback. Please resubmit to a >> new CF when you have an updated patch. > > There are no updates from about two years before, but this patch > has been registered in CF 2020-03. Not sure why. It should be marked > as Returned with Feedback again? Worse, it was marked Needs Review even though no new patch was provided. I'm going to set this back to Returned with Feedback. If anyone has a good reason that it should be in the CF we can always revive it. Regards, -- -David david@pgmasters.net
Commits
-
Implement waiting for given lsn at transaction start
- 0f5ca02f53ac 13.0 landed