Re: [HACKERS] Replication status in logical replication

Поиск
Список
Период
Сортировка
От Simon Riggs
Тема Re: [HACKERS] Replication status in logical replication
Дата
Msg-id CANP8+jK4WF7ZxwvfhnNGsqkEO6JbwcPYtUO7Zr3RmVwgDh78fA@mail.gmail.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Replication status in logical replication  (Masahiko Sawada <sawada.mshk@gmail.com>)
Ответы Re: [HACKERS] Replication status in logical replication
Список pgsql-hackers
Дерево обсуждения 
On 9 January 2018 at 04:36, Masahiko Sawada <sawada.mshk@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.

-- 
Simon Riggs                http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

В списке pgsql-hackers по дате отправления:

Предыдущее
От: Simon Riggs
Дата:
Сообщение: Re: Changing WAL Header to reduce contention during ReserveXLogInsertLocation()
Следующее
От: Fabien COELHO
Дата:
Сообщение: Re: [HACKERS] Re: [COMMITTERS] pgsql: Remove pgbench "progress" testpending solution of its timing is (fwd)