Re: [HACKERS] Logical replication launcher's bgworker enabled bydefault, and max_logical_replication_workers
| От | Jaime Casanova |
|---|---|
| Тема | Re: [HACKERS] Logical replication launcher's bgworker enabled bydefault, and max_logical_replication_workers |
| Дата | |
| Msg-id | CAJGNTeMEK+878LPGY-42m6O13NYi4zAcC-+zzP=6iM2zuOnsTw@mail.gmail.com обсуждение исходный текст |
| Ответ на | [HACKERS] Logical replication launcher's bgworker enabled by default, and max_logical_replication_workers (Michael Paquier <michael.paquier@gmail.com>) |
| Ответы |
Re: [HACKERS] Logical replication launcher's bgworker enabled bydefault, and max_logical_replication_workers
|
| Список | pgsql-hackers |
On 22 January 2017 at 23:37, Michael Paquier <michael.paquier@gmail.com> wrote: > Hi all, > > When spawning a new instance, I found the following thing, which is > surprising at first sight: > postgres: bgworker: logical replication launcher > This is because the downstream needs it https://www.postgresql.org/message-id/CAMsr%2BYHH2XRUeqWT6pn_X0tFpP5ci7Fsrsn67TDXbFLeMknhBA%40mail.gmail.com > In the same range of thoughts, it is also surprising to have the > default value of max_logical_replication_workers set to 4, I would > have thought that for a feature that has created more than 13k of code > diffs, it would be disabled by default. > +1, we should that to 0 before release -- Jaime Casanova www.2ndQuadrant.com PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
В списке pgsql-hackers по дате отправления: