Re: [HACKERS] Logical Replication WIP - Mailing list pgsql-hackers

From Jaime Casanova
Subject Re: [HACKERS] Logical Replication WIP
Date
Msg-id CAJGNTeP-JC_2SoEsW_VncPoX=FuadPs3KNTZBdkBcQR=Z8svJA@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Logical Replication WIP  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
Responses Re: [HACKERS] Logical Replication WIP  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
On 20 January 2017 at 11:25, Petr Jelinek <petr.jelinek@2ndquadrant.com> wrote:
> On 20/01/17 17:05, Fujii Masao wrote:
>> On Fri, Jan 20, 2017 at 11:08 PM, Peter Eisentraut
>> <peter.eisentraut@2ndquadrant.com> wrote:
>>> On 1/19/17 5:01 PM, Petr Jelinek wrote:
>>>> There were some conflicting changes committed today so I rebased the
>>>> patch on top of them.
>>>>
>>>> Other than that nothing much has changed, I removed the separate sync
>>>> commit patch, included the rename patch in the patchset and fixed the
>>>> bug around pg_subscription catalog reported by Erik Rijkers.
>>>
>>> Committed.
>>
>> Sorry I've not followed the discussion about logical replication at all, but
>> why does logical replication launcher need to start up by default?
>>
>
> Because running subscriptions is allowed by default. You'd need to set
> max_logical_replication_workers to 0 to disable that.
>

surely wal_level < logical shouldn't start a logical replication
launcher, and after an initdb wal_level is only replica


-- 
Jaime Casanova                      www.2ndQuadrant.com
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services



pgsql-hackers by date:

Previous
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical Replication WIP
Next
From: Petr Jelinek
Date:
Subject: Re: [HACKERS] Logical Replication WIP