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

From Fujii Masao
Subject Re: [HACKERS] Logical Replication WIP
Date
Msg-id CAHGQGwHCLo3TFbMWoOXuLBPLwjxXJG5ws_2ur1mXOxcyi-w1MQ@mail.gmail.com
Whole thread Raw
In response to Re: [HACKERS] Logical Replication WIP  (Peter Eisentraut <peter.eisentraut@2ndquadrant.com>)
Responses Re: [HACKERS] Logical Replication WIP  (Petr Jelinek <petr.jelinek@2ndquadrant.com>)
List pgsql-hackers
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?
   $ initdb -D data   $ pg_ctl -D data start

When I ran the above commands, I got the following message and
found that the bgworker for logical replicatdion launcher was running.
   LOG:  logical replication launcher started

Regards,

-- 
Fujii Masao



pgsql-hackers by date:

Previous
From: "Joshua D. Drake"
Date:
Subject: Re: [HACKERS] Packages: Again
Next
From: Tom Lane
Date:
Subject: Re: [HACKERS] pgbench - allow backslash continuations in \set expressions