From: | Petr Jelinek <petr(dot)jelinek(at)2ndquadrant(dot)com> |
---|---|
To: | Michael Paquier <michael(dot)paquier(at)gmail(dot)com>, PostgreSQL mailing lists <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Logical replication launcher's bgworker enabled by default, and max_logical_replication_workers |
Date: | 2017-01-23 17:48:11 |
Message-ID: | 9d4d3b3e-7460-3ba3-03ef-6f7ec2dd4197@2ndquadrant.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 23/01/17 05:37, Michael Paquier wrote:
> Hi all,
>
> When spawning a new instance, I found the following thing, which is
> surprising at first sight:
> postgres: bgworker: logical replication launcher
>
> There is perhaps no problem to keep that enabled by default until the
> release 10 wraps to give it some buildfarm coverage similarly to what
> has been done last year for parallel query, but what is surprising me
> is that even if wal_level is *not* logical this gets started. I think
> that something like the patch attached is needed, so as
> ApplyLauncherRegister() is a noop if wal_level < logical.
>
As discussed elsewhere, there is no need for wal_level = logical
downstream and launcher is only needed for downstream.
--
Petr Jelinek http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Training & Services
From | Date | Subject | |
---|---|---|---|
Next Message | David G. Johnston | 2017-01-23 17:49:06 | Re: Undefined psql variables |
Previous Message | Jeff Davis | 2017-01-23 17:45:03 | Re: Review: GIN non-intrusive vacuum of posting tree |