Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eQDLp-0000zS-5e for pgsql-docs@arkaria.postgresql.org; Sat, 16 Dec 2017 14:22:05 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eQDLo-00074v-I0 for pgsql-docs@arkaria.postgresql.org; Sat, 16 Dec 2017 14:22:04 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eQDLn-00074l-SB for pgsql-docs@lists.postgresql.org; Sat, 16 Dec 2017 14:22:04 +0000 Received: from out3-smtp.messagingengine.com ([66.111.4.27]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.89) (envelope-from ) id 1eQDLk-0007Pl-R4 for pgsql-docs@postgresql.org; Sat, 16 Dec 2017 14:22:03 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id 8C2E520BB1; Sat, 16 Dec 2017 09:21:58 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute7.internal (MEProxy); Sat, 16 Dec 2017 09:21:58 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=fQU16N RCyyX1HSYr4rbK/q7725YKmMVvvua0kmhr8R0=; b=SiCnwH1WlqSAHSSa+QtRKD kNNuzWxsZPXPVQHx86BpSgePQBucZ6BY7XM9rh2sKYbn9gE0EEweqmaNkXISkbhp 1Aincfkd3sHgE4+W++L2bGarPMwr1LyNLxYfmglJjuo5n1Lo5vRx+NFl9cDOUFfu XQNApzk6P2G8ceRxc8u40wemyDfpdaKojWdzcXis6q6BLW7qhuF68HsONPxkZMMw +hostXHcO3ASN0vUtIVS0Y+ah/aI+L/MsqflnouVaYPl6/UHqYg1QSjb8tsbUioY ntUIBenM5k1Tj40R3RjVooFdfM/gmJfC7grr+ed0xpwKiAJopenSiScdNJSBBaaw == X-ME-Sender: Received: from april.local (c-73-13-66-39.hsd1.pa.comcast.net [73.13.66.39]) by mail.messagingengine.com (Postfix) with ESMTPA id 45F4624235; Sat, 16 Dec 2017 09:21:58 -0500 (EST) Subject: Re: State which instances must have "wal_level=logical" in Logical Replication in Postgres 10 To: contact@gurpartap.com, pgsql-docs@postgresql.org References: <20171216134051.29862.2884@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <836b3ba2-a145-7e0f-02ca-78260bb74a42@2ndquadrant.com> Date: Sat, 16 Dec 2017 09:21:57 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0 MIME-Version: 1.0 In-Reply-To: <20171216134051.29862.2884@wrigleys.postgresql.org> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On 12/16/17 08:40, contact@gurpartap.com wrote: > Page: https://www.postgresql.org/docs/10/static/logical-replication-quick-setup.html > Description: > > Hello! > > In a logical replication setup, this guide needs to explicitly help the user > identify the postgresql instances that must have "wal_level = logical" > defined. That is explained in the section before the one you are looking at. -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services