Re: Improvement in log message of logical replication worker

From: Peter Eisentraut <peter(dot)eisentraut(at)2ndquadrant(dot)com>
To: Masahiko Sawada <sawada(dot)mshk(at)gmail(dot)com>, Robert Haas <robertmhaas(at)gmail(dot)com>
Cc: PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Improvement in log message of logical replication worker
Date: 2017-05-17 16:00:45
Message-ID: e371639b-154e-28fd-46d6-c8217e1ff674@2ndquadrant.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: 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

In response to

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Remi Colinet 2017-05-17 16:13:42 Re: [PATCH v2] Progress command to monitor progression of long running SQL queries
Previous Message Peter Eisentraut 2017-05-17 15:55:11 Re: [COMMITTERS] pgsql: Preventive maintenance in advance of pgindent run.