Re: [HACKERS] Improvement in log message of logical replicationworker

Поиск
Список
Период
Сортировка
От Peter Eisentraut
Тема Re: [HACKERS] Improvement in log message of logical replicationworker
Дата
Msg-id e371639b-154e-28fd-46d6-c8217e1ff674@2ndquadrant.com
обсуждение исходный текст
Ответ на Re: [HACKERS] Improvement in log message of logical replication worker  (Masahiko Sawada <sawada.mshk@gmail.com>)
Ответы Re: [HACKERS] Improvement in log message of logical replication worker  (Masahiko Sawada <sawada.mshk@gmail.com>)
Список pgsql-hackers
Дерево обсуждения 
On 5/17/17 05:15, Masahiko Sawada wrote:
> BTW, why should max_replication_slots be set more than 0 even on the
> subscriber side? It's documented but I could not understand reason.

Because that setting also controls replication origin tracking slots.

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

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

Предыдущее
От: Peter Eisentraut
Дата:
Сообщение: Re: [HACKERS] [COMMITTERS] pgsql: Preventive maintenance in advanceof pgindent run.
Следующее
От: Remi Colinet
Дата:
Сообщение: Re: [HACKERS] [PATCH v2] Progress command to monitor progression oflong running SQL queries