Re: [HACKERS] Replication status in logical replication
От | Masahiko Sawada |
---|---|
Тема | Re: [HACKERS] Replication status in logical replication |
Дата | |
Msg-id | CAD21AoCfDxYpRLn-i8jiMHiJ5kjkubjMVMNXOmW0--6iU=eQYA@mail.gmail.com обсуждение исходный текст |
Ответ на | Re: [HACKERS] Replication status in logical replication (David Steele <david@pgmasters.net>) |
Ответы |
Re: [HACKERS] Replication status in logical replication
|
Список | pgsql-hackers |
On Tue, Apr 10, 2018 at 11:11 PM, David Steele <david@pgmasters.net> wrote: > On 4/10/18 6:14 AM, Masahiko Sawada wrote: >> On Fri, Mar 30, 2018 at 5:37 AM, Fujii Masao <masao.fujii@gmail.com> wrote: >>> On Wed, Jan 17, 2018 at 2:16 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >>>> On 16 January 2018 at 06:21, Michael Paquier <michael.paquier@gmail.com> wrote: >>>>> On Tue, Jan 16, 2018 at 10:40:43AM +0900, Masahiko Sawada wrote: >>>>>> On Sun, Jan 14, 2018 at 12:43 AM, Simon Riggs <simon@2ndquadrant.com> wrote: >>>>>>> On 9 January 2018 at 04:36, Masahiko Sawada <sawada.mshk@gmail.com> wrote: >>>>>>> We're not talking about standbys, so the message is incorrect. >>>>>> >>>>>> Ah, I understood. How about "\"%s\" has now caught up with upstream >>>>>> server"? >>>>> >>>>> +1. >>>> >>>> upstream is what I would have suggested, so +1 here also. >>>> >>>> Will commit. >>> >>> ping? >>> >> >> Should I add this item to "Older Bugs" of the open item since we >> regarded it as a bug? > > I'm going to reclassify this as a bug since everyone seems to agree it > is one. I've added this to Open Items so as not to forget. Regards, -- Masahiko Sawada NIPPON TELEGRAPH AND TELEPHONE CORPORATION NTT Open Source Software Center
В списке pgsql-hackers по дате отправления: