On Sun, Jan 14, 2018 at 12:43 AM, Simon Riggs <si...@2ndquadrant.com> wrote: > On 9 January 2018 at 04:36, Masahiko Sawada <sawada.m...@gmail.com> wrote: > >>> This patch appears to cause this DEBUG1 message >>> >>> "standby \"%s\" has now caught up with primary" >>> >>> which probably isn't the right message, but might be OK to backpatch. >>> >>> Thoughts on better wording? >>> >> >> I think that this DEBUG1 message appears when sent any WAL after >> caught up even without this patch. This patch makes this message >> appear at a properly timing. Or am I missing something? > > We're not talking about standbys, so the message is incorrect. >
Ah, I understood. How about "\"%s\" has now caught up with upstream server"? Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
