Re: [HACKERS] max_sync_workers_per_subscription is missing inpostgresql.conf - Mailing list pgsql-hackers

From Petr Jelinek
Subject Re: [HACKERS] max_sync_workers_per_subscription is missing inpostgresql.conf
Date
Msg-id f9c00734-b10a-0e76-84be-251af62083da@2ndquadrant.com
Whole thread Raw
In response to [HACKERS] max_sync_workers_per_subscription is missing in postgresql.conf  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: [HACKERS] max_sync_workers_per_subscription is missing in postgresql.conf  (Masahiko Sawada <sawada.mshk@gmail.com>)
List pgsql-hackers
On 10/04/17 07:16, Masahiko Sawada wrote:
> Hi all,
> 
> Attached a patch for $subject.
> 
> I added this parameter into "Asynchronous Behavior" section of
> "RESOURCE" section. But GUC parameter for subscriber now is written in
> this section, in spite of there is "REPLICATION" section. I think that
> we can coordinate these parameters to not confuse user. For example in
> documentation, these parameters are described in "19.6.4. Subscribers"
> section of "19.6. Replication" section. Thought?
> 

Good catch, but it's actually taken from max_logical_replication_workers
so the patch should look more like attached IMHO.

-- 
  Petr Jelinek                  http://www.2ndQuadrant.com/
  PostgreSQL Development, 24x7 Support, Training & Services

-- 
Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-hackers

Attachment

pgsql-hackers by date:

Previous
From: Michael Paquier
Date:
Subject: Re: [HACKERS] Compiler warning in costsize.c
Next
From: Masahiko Sawada
Date:
Subject: Re: [HACKERS] max_sync_workers_per_subscription is missing in postgresql.conf