Re: Improvement in log message of logical replication worker

From: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>
To: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
Cc: Robert Haas <robertmhaas(at)gmail(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improvement in log message of logical replication worker
Date: 2017-05-18 03:37:36
Message-ID: CAD21AoBb3QM7aGBLWXSQYk6+VQk+32wFvk-boq_nQh3dQbDNEw@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Thu, May 18, 2017 at 1:00 AM, Peter Eisentraut
<peter(dot)eisentraut(at)2ndquadrant(dot)com> wrote:
> 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.
>

Thanks! I understood the reason.

Regards,

--
Masahiko Sawada
NIPPON TELEGRAPH AND TELEPHONE CORPORATION
NTT Open Source Software Center

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Amit Kapila 2017-05-18 03:43:55 Re: UPDATE of partition key
Previous Message Masahiko Sawada 2017-05-18 03:36:46 Re: Improvement in log message of logical replication worker