Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZjiR-0004Xy-8c for pgsql-docs@arkaria.postgresql.org; Thu, 11 Jan 2018 20:44:47 +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 1eZjiQ-0002j3-M0 for pgsql-docs@arkaria.postgresql.org; Thu, 11 Jan 2018 20:44:46 +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 1eZjiQ-0002iu-AE for pgsql-docs@lists.postgresql.org; Thu, 11 Jan 2018 20:44:46 +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 1eZjiL-0001qT-W0 for pgsql-docs@lists.postgresql.org; Thu, 11 Jan 2018 20:44:45 +0000 Received: from compute7.internal (compute7.nyi.internal [10.202.2.47]) by mailout.nyi.internal (Postfix) with ESMTP id D06D820AF0; Thu, 11 Jan 2018 15:44:39 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute7.internal (MEProxy); Thu, 11 Jan 2018 15:44:39 -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=d8PzTB 4pJ64/zguAl2pkSq22bgIoo2osqA8a1zaSwsc=; b=eZtEy7w50SkPl0CNazUf2R eD8qZm+BO/2Tnna/lf8XGi+RYIpt/IIzyPGLMnDDnM1YAwAeXjWBd13rhHhdhVsp 2O1kLv+dpu97nK53UuW8tRhCSkaRZytG+EcS8Pg6jNkw32HhaDnW5Aq+Ri+8u51L znea2ksaZdmpsOMygIkewUpsHsfPZhlzplSgGDL6EOcRfqZmdK0X+PvpMQGJE1Y0 iUyf2B8HMqwLIrJAkR8zeOnMybvT/F/5/4gku9tGzXQMrfd9lRcXXDRKkLD0JHWO GpL1A55/24zIDLCNK8n1uoBaLlf1Iu7msi8eE4bNoUSYsW0RkcDaUF+YUC6abd6A == 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 8E9BD7E354; Thu, 11 Jan 2018 15:44:39 -0500 (EST) Subject: Re: Regarding built-in logical replication To: ranjangajare@gmail.com, pgsql-docs@lists.postgresql.org References: <20180111144829.1423.39917@wrigleys.postgresql.org> From: Peter Eisentraut Organization: 2ndQuadrant Message-ID: <207da7bc-3b31-df40-7906-2addabd22822@2ndquadrant.com> Date: Thu, 11 Jan 2018 15:44:39 -0500 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.2 MIME-Version: 1.0 In-Reply-To: <20180111144829.1423.39917@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 1/11/18 09:48, PG Doc comments form wrote: > The following documentation comment has been logged on the website: > > Page: https://www.postgresql.org/docs/10/static/logical-replication.html > Description: > > I am referring to link > 'https://www.postgresql.org/docs/10/static/logical-replication.html' and it > has been mentioned that 'Replicating between different major versions of > PostgreSQL.' under the section of 'The typical use-cases for logical > replication are:' but I don't think logical replication using > PUBLICATION/SUBSCRIPTION model is possible between different PostgreSQL > versions, which is only possible using pglogical. The documentation is correct. (The only caveat is that there are currently no other versions than 10 that have built-in logical replication, but if there were any, it would work.) -- Peter Eisentraut http://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services