Re: Separate GUC for replication origins

Поиск
Список
Период
Сортировка
От Euler Taveira
Тема Re: Separate GUC for replication origins
Дата
Msg-id 63cecd67-6a54-4b2d-bef1-b25a34f9c48c@app.fastmail.com
обсуждение исходный текст
Ответ на Re: Separate GUC for replication origins  (Masahiko Sawada <sawada.mshk@gmail.com>)
Ответы Re: Separate GUC for replication origins
Список 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

Вложения

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