Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mdXy5-0001Jo-KI for pgsql-admin@arkaria.postgresql.org; Thu, 21 Oct 2021 13:18:49 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1mdXy4-00051h-Gb for pgsql-admin@arkaria.postgresql.org; Thu, 21 Oct 2021 13:18:48 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1mdXy4-00051X-2e for pgsql-admin@lists.postgresql.org; Thu, 21 Oct 2021 13:18:48 +0000 Received: from mail-ot1-x333.google.com ([2607:f8b0:4864:20::333]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1mdXxx-0006Xw-LB for pgsql-admin@postgresql.org; Thu, 21 Oct 2021 13:18:47 +0000 Received: by mail-ot1-x333.google.com with SMTP id l10-20020a056830154a00b00552b74d629aso385790otp.5 for ; Thu, 21 Oct 2021 06:18:41 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=enterprisedb.com; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=rKECnZy6YhNaR2UVozFvIp/R1+HvZGiyQPRdjtS4QrM=; b=BCbpyMOvRZ0LmvcEeOcIndwVvA2gCPx1qVyrYHSyQ6g/LwO8xBRKrt7mOphCPS8lp8 7IfWpq9mmZ0soIGdsbT0fowNx2WXjd3vfenldDcnX2Pl2l8ZXpm9F6zLQJmPyJaed/OP 4b7aiWAHMLBLrRBVEuRs+SD0rzcVTmvj8fyU6w2PxRdPhU3UtT2eamg8y67o0MMtbWr3 6hmUtb5VSn242obfM/nDhrblOChRHlrsbi3SvuIIBqC1jKb9XEUUhhD+6j856kMG/NW0 aQ+fld9ixveMemwhJMyMtUAoYjl/IyxmmWDXOPe+j7SIeTDN+ibRIacMQaW96YUDND44 87bg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=rKECnZy6YhNaR2UVozFvIp/R1+HvZGiyQPRdjtS4QrM=; b=fEZMbtBpv87BV+YTCfh5tIf0ZsvT+X6roODFBG55OAvXWw2Ppi7+swr4V94KvBNl3l vhsRAzKaxXCA6WAbx5an2Z/RmCLx3qMFs9aRbtQxkOjRdKWSLEIBGKGARZvlWbYXPCKa IFbNcqODARsYZrktA7x0mEUZulENL8xPwfYLlcRWFX1Okf81upLaZ0plCsv7zpm3Z15p G5eznmFq+M0U6FB7eiJICRdiBzXGH/vdNuD+0u7t889by3Lc7eXib3cs+x1rU5t0KdEM pDQcaC6Bk2GSIDJfWHF/EfXHmcukFiZdRRmftJFH96/uS6DUl356YeKL3xRaenC1f5rI 6vnQ== X-Gm-Message-State: AOAM530NYVfIqwE/mJGbTS7GDSzn+Z7stQSM0cVWYuW1rl6bg0mbOtR7 TOnooKmzGYQT6ctmKx4kCPKeE8aUKXD2bHTsY1Hljtg432dhm4fKepK/PggOTbmBCa+Sr0UK9q7 uTw9/0VnJfeDJuI0eQHV211opFPBld+lZ+M2y5E4Kx55EC+lVmgJqV2Pez9GuGKI6B8ZOIXQw8n GiZ8Dys5dL3AMAPbCSFrwL+Va9awLQOENSJ1vn+wKdmKEhQFn3yCyEtro= X-Google-Smtp-Source: ABdhPJwAWj4Bm9v/jzqvIwUIDdLsLv6IOuGZL/s5wP4s+K3B8xAsEgjchqCZF7Sjw6JGrHS6UaOjwsqelsirDvWwUyE= X-Received: by 2002:a05:6830:1482:: with SMTP id s2mr4852333otq.382.1634822320970; Thu, 21 Oct 2021 06:18:40 -0700 (PDT) MIME-Version: 1.0 References: <8381e958-e437-cc8c-f912-02bfd420cead@quadratum-braccas.com> In-Reply-To: <8381e958-e437-cc8c-f912-02bfd420cead@quadratum-braccas.com> From: Simon Riggs Date: Thu, 21 Oct 2021 14:18:29 +0100 Message-ID: Subject: Re: Can I make logical replication behave like synchronous streaming? To: sbob Cc: pgsql-admin Content-Type: text/plain; charset="UTF-8" X-CLOUD-SEC-AV-Info: enterprisedb,google_mail,monitor X-CLOUD-SEC-AV-Sent: true X-Gm-Spam: 0 X-Gm-Phishy: 0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, 20 Oct 2021 at 22:47, sbob wrote: > We are going to be replication across platforms (risc ti intel), so we > will be using logical replication (PostgreSQL v11) > > However we need a synchronous solution as opposed to async. > > > Does logical replication perform like synchronous streaming? If not can > I force it to do so? Yes, it is designed to use the same connection interfaces. https://www.postgresql.org/docs/devel/logical-replication-subscription.html Note that sync rep in this mode is equivalent to synchronous_commit = remote_apply. -- Simon Riggs http://www.EnterpriseDB.com/