Re: Separate GUC for replication origins - Mailing list pgsql-hackers

From Euler Taveira
Subject Re: Separate GUC for replication origins
Date
Msg-id 63cecd67-6a54-4b2d-bef1-b25a34f9c48c@app.fastmail.com
Whole thread Raw
In response to Re: Separate GUC for replication origins  (Masahiko Sawada <sawada.mshk@gmail.com>)
Responses Re: Separate GUC for replication origins
List pgsql-hackers
On Mon, Mar 17, 2025, at 8:44 PM, Masahiko Sawada wrote:
I would suggest putting the new max_active_replication_origins after
max_parallel_apply_workers_per_subscription as both
max_sync_workers_per_subscription and
max_parallel_apply_workers_per_subscription are related to
max_logical_replication_workers.

Good point. Looking at the documentation, the old max_replication_slots
parameter was the first one in that section so I decided to use the same order
for the postgresql.conf.sample.


--
Euler Taveira

Attachment

pgsql-hackers by date:

Previous
From: Sungwoo Chang
Date:
Subject: Re: dsm_registry: Add detach and destroy features
Next
From: David Rowley
Date:
Subject: Re: maintenance_work_mem = 64kB doesn't work for vacuum