Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iRroC-00068f-1I for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2019 05:55:16 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1iRro9-0006pv-AV for pgsql-general@arkaria.postgresql.org; Tue, 05 Nov 2019 05:55:13 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1iRro8-0006pj-R7; Tue, 05 Nov 2019 05:55:13 +0000 Received: from mail-pg1-x544.google.com ([2607:f8b0:4864:20::544]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1iRro6-0007Qk-BH; Tue, 05 Nov 2019 05:55:11 +0000 Received: by mail-pg1-x544.google.com with SMTP id 29so1910834pgm.6; Mon, 04 Nov 2019 21:55:10 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=date:message-id:to:cc:subject:from:in-reply-to:references :user-agent:mime-version:content-transfer-encoding; bh=h55pSMCRTPtRokmJ5S9GmN4oHubiyNO7qJef1CKwQhw=; b=Ac6QTpDx7NNQ4/ixwIzlWC9C3PtrdBg9UM1va3QWKLIhMYH1feym31u96YWS5aOub6 IcDLxIJKQVVIOGuFdJRkY0Po9q9F3kk8JC7/XBvmxVVAV/fLVQdSY/5CPMN+OpiyU1E4 5EMu8Q8tSZ6Q1pM03mrtOyig8uCoFt2ysby+KJr6OYJXWtG4k6efXV8yNCfUcKskiUMM kiGeXL3ZIDZ5p7HfAFUqVzu2/W/rGn50ep1n8+ATG6bK8rwBrtrP5xDfvHsSyuSPSv6P N97escFaStJ/Ptiycf9nvQBd0VjQvpQiIw4Fcivn0rlupTRT1/LvdK5cBCZ7CYO/gYHp UWzQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:message-id:to:cc:subject:from:in-reply-to :references:user-agent:mime-version:content-transfer-encoding; bh=h55pSMCRTPtRokmJ5S9GmN4oHubiyNO7qJef1CKwQhw=; b=odDw895inC3QzHxiSiSAtxtUx2LtBrjRbG21m55vArj6K+3H1LvezzRimXNjWd2eOw p7Y4pQUOiTIGJCCVEE6qHJn/cOt0wkmhhYwiKgr1/+15NtDljmTxdRXEw0VTHp54ITVD nmxJiibbinHE/VV0VcgAJwD7XcLUPTZ+0mcndGK/drgabDwEhDbuZHIsqqwY4V6LCl9J DyeH8caXxjxYY3eq6Ub4XA9Cs3nSvSWUTtNDsaDSemy8XBfrWsPQ1xglHjbom2/U9NVe L20pjkYfmKC3MtqcJkrXZa+YBJmIu7vH7SHELPkSXoD5wDO8ZaUeevom2btHMILJOvQS LbNw== X-Gm-Message-State: APjAAAWOZVXnGKTPVWNQ6gxtOIYSATl0zO6jgc0r6M0+zeHFZSQH2j3Z 0RysWyCTNkL/bVw4pjIvBzo= X-Google-Smtp-Source: APXvYqxGim9sEKTt5THys2sDv3aYRb5LwtTND8MgunLXok8cXdTRv6YOJ1wlod8yo5uATrcgTup6Xg== X-Received: by 2002:a63:af1a:: with SMTP id w26mr35213489pge.251.1572933308982; Mon, 04 Nov 2019 21:55:08 -0800 (PST) Received: from localhost (w199058.dynamic.ppp.asahi-net.or.jp. [121.1.199.58]) by smtp.gmail.com with ESMTPSA id f59sm20140158pje.0.2019.11.04.21.55.06 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 04 Nov 2019 21:55:08 -0800 (PST) Date: Tue, 05 Nov 2019 14:54:41 +0900 (JST) Message-Id: <20191105.145441.1121905199858654119.horikyota.ntt@gmail.com> To: ashokt@ohumhealthcare.com Cc: rui@crazybean.net, brightuser2019@gmail.com, pgsql-general@lists.postgresql.org, pgsql-admin@lists.postgresql.org Subject: Re: Create a logical and physical replication From: Kyotaro Horiguchi In-Reply-To: References: User-Agent: Mew version 6.8 on Emacs 26.1 Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk Hello. At Mon, 4 Nov 2019 19:05:24 +0530, Ashok Kumar Tiwari wrote in > is it possible in postgres to create one physical replica for DR(data > recovery purpose) and another one logical replica for reporting purpose A physical replication standby cannot be a publisher. You will find that CREATE PUBLICATION fails. > master --------> physical standby (for DR Purpose) > | > | > | > | > logical replica for reporting purpose > > ------------------ or cascading logic replication > > master --------> physical standby (for DR Purpose) ------------- > > logical replica for reporting purpose The former works (as documented in [1]) but the latter doesn't. By the way, If I'm not missing anything I don't find a description on this restriction in the documentation. Shouldn't it be in [2], or [1]? [1]: https://www.postgresql.org/docs/12/logical-replication.html [2]: https://www.postgresql.org/docs/12/logical-replication-restrictions.html regards. -- Kyotaro Horiguchi NTT Open Source Software Center