Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eZr2m-0005ob-KQ for pgsql-docs@arkaria.postgresql.org; Fri, 12 Jan 2018 04:34:16 +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 1eZr2k-0006JE-Nj for pgsql-docs@arkaria.postgresql.org; Fri, 12 Jan 2018 04:34:14 +0000 Received: from makus.postgresql.org ([2001:4800:1501:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA384:256) (Exim 4.84_2) (envelope-from ) id 1eZovM-0000od-CM for pgsql-docs@lists.postgresql.org; Fri, 12 Jan 2018 02:18:28 +0000 Received: from mail-vk0-x243.google.com ([2607:f8b0:400c:c05::243]) by makus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1eZovJ-00056z-CR for pgsql-docs@lists.postgresql.org; Fri, 12 Jan 2018 02:18:27 +0000 Received: by mail-vk0-x243.google.com with SMTP id n4so2772399vkd.6 for ; Thu, 11 Jan 2018 18:18:24 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=u0IIUIsBb5+QDug1Ici/W0KRJxaX2sxDwtJtFadjt98=; b=ZoDvc/K6ANjuZrNcz7XxTdoLuNbJ+2fFxixAtReW8em2x+HrGnMQKRobSNtgkiXqjq ZUPg0GHmPbp+TGSxked+t9HdsfvkHryokMlIaw7RHN7XJa3cFV5hXvU/+988MHdoaSYA BODNSrQg/1R4akz9/GlhYjFFFCMVGWqsnEFepGj59pGKPkxKDlVY0ecLOecpU0MgnN1y fbEdxGTu5BO1UNofX+efTUr+2xLW1iqqu0XKwejmYnv9ZDk0eNIMvmtmv/rPw+hNTuhz UHFgMlUOhbSDcTYSmRNcmmgREq3VY3j81FgA4jaSpH3ZNkZf6KGLwzm0s5klDlzf8nfK ZG1Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=u0IIUIsBb5+QDug1Ici/W0KRJxaX2sxDwtJtFadjt98=; b=qwcn1MzV5TaXuDE/NMc/pELaZPk5nOeJB0EX9ymHkAN0/u/DLP8XDy7HhViR3e2XZE YytXfSJfqvXoWo8NHco287J8rubMvLTopUrt6S58l+KRa+nZVvzUiohBCvQUGXxMn/4P QrsFJk56qQsXwQiZDeO7IozSaSIY5IKvdMF+ReVOQlqUAID+Opb4pfEVP8yv4KEoQZb+ SrMKoUguQxS7/pjmytE0hITpLkY5JCevg5yC8PQCTcx70tyluKZLfOvFuw+N3CC+k6OF tHGhaJ2jNy/AnfnG+fGknHBViezj8t0GUZG1xXHy9vbNQybxjRBsvpit3ZvB6evOMCpn O8Yg== X-Gm-Message-State: AKwxytfCVK0f1IAdJaueQ+QWJjrXdeLxSbzdOVUeAj7XU15L8ZbgJVhB w3vtknRM6YHVwZcuDpcIClEYfQBiFq0dJJ+CleFhMQ== X-Google-Smtp-Source: ACJfBosHOlZqkfThrs6FEPASihza3aqisbHvIlwt1MYdI9HBEEWcn3kwYQK1b19CEHYjv8N9cDb5o3Ky/EpZ2gL4qdY= X-Received: by 10.31.242.204 with SMTP id q195mr7192100vkh.188.1515723502654; Thu, 11 Jan 2018 18:18:22 -0800 (PST) MIME-Version: 1.0 Received: by 10.176.10.154 with HTTP; Thu, 11 Jan 2018 18:18:22 -0800 (PST) Received: by 10.176.10.154 with HTTP; Thu, 11 Jan 2018 18:18:22 -0800 (PST) In-Reply-To: <207da7bc-3b31-df40-7906-2addabd22822@2ndquadrant.com> References: <20180111144829.1423.39917@wrigleys.postgresql.org> <207da7bc-3b31-df40-7906-2addabd22822@2ndquadrant.com> From: Ranjan Gajare Date: Fri, 12 Jan 2018 07:48:22 +0530 Message-ID: Subject: Re: Regarding built-in logical replication To: Peter Eisentraut Cc: pgsql-docs@lists.postgresql.org Content-Type: multipart/alternative; boundary="94eb2c14c202f41b4005628ae096" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk --94eb2c14c202f41b4005628ae096 Content-Type: text/plain; charset="UTF-8" This means it would work with version 10 and its later versions. No backward compatibility is possible. Thanks for resolution. Ranjan Gajare On 12-Jan-2018 2:14 AM, "Peter Eisentraut" wrote: 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 --94eb2c14c202f41b4005628ae096 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
This means it would work with vers= ion 10 and its later versions. No backward compatibility is possible.
=
Thanks for resolut= ion.=C2=A0

Ranjan Gajare


On 12-Jan-2018 2:14 AM, "Peter Eisentraut" <<= a href=3D"mailto:peter.eisentraut@2ndquadrant.com">peter.eisentraut@2ndquad= rant.com> wrote:
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.o= rg/docs/10/static/logical-replication.html' and it
> has been mentioned that 'Replicating between different major versi= ons of
> PostgreSQL.' under the section of 'The typical use-cases for l= ogical
> replication are:' but I don't think logical replication using<= br> > PUBLICATION/SUBSCRIPTION model is possible between different PostgreSQ= L
> 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=C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 http://w= ww.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

--94eb2c14c202f41b4005628ae096--