Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szUG5-006KT4-Di for pgsql-docs@arkaria.postgresql.org; Sat, 12 Oct 2024 05:01:41 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1szUG2-00HOhU-J0 for pgsql-docs@arkaria.postgresql.org; Sat, 12 Oct 2024 05:01:38 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1szUG2-00HOhJ-A3 for pgsql-docs@lists.postgresql.org; Sat, 12 Oct 2024 05:01:38 +0000 Received: from mail-wm1-x32a.google.com ([2a00:1450:4864:20::32a]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1szUFz-000TDf-Qm for pgsql-docs@lists.postgresql.org; Sat, 12 Oct 2024 05:01:37 +0000 Received: by mail-wm1-x32a.google.com with SMTP id 5b1f17b1804b1-4311420b675so22926115e9.2 for ; Fri, 11 Oct 2024 22:01:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=cybertec.at; t=1728709293; x=1729314093; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:from:to:cc:subject:date :message-id:reply-to; bh=ZC+O/iYRqx3+fqUTyyu68kkUNlEQ9QEdCjfrBAKliYA=; b=T9S0EtAjH4CKsRDnbqC0kpjGzS5Hn19xy49DoNr5rhyOZebv4cuIBnCmYLnNxN2I9f lfudoQoAZkpQub5cX3+Bq3QR24QeDEiaOj5MNZ6CSiIBBvkACWxCpL8CemPjSCWqF7Js JMYMndy0hJYETJZHQzB7rljHSRLaMYuC/pNcE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1728709293; x=1729314093; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:to:from:subject:message-id:x-gm-message-state:from :to:cc:subject:date:message-id:reply-to; bh=ZC+O/iYRqx3+fqUTyyu68kkUNlEQ9QEdCjfrBAKliYA=; b=aG1MYpxRbY9ZJgjulvqDK36VsDRm4mfNLBtDRktXQzjuUCUhNywa2ErVwLuyLmQEgN CMBZnGSfaymWv9BsxcgwuRpnJNHOZ5CKs/TZ3k6Mo5Y5OXzMuhvbXRT6gm/XMxJrZPnx Sbuco8t4yhXckHl7t4iJehCue7bDfDTN1Gyk2jKjlFH8lPS5+5Ru5tvYb1HtzNxltfYH aF74codKqOSbg1QbKsoP3WTiRfMvh2l2dKQ6x5zbA6Qh0sQdyHn57Ic69g+g2DqtgdRR ZnAnhyBFLadO+MobryGq8O2annG45Q1seJT/w4HZijEB+d2WUA6SvMN6QMkDaPAdLbuZ I9rg== X-Forwarded-Encrypted: i=1; AJvYcCUbU8DCdxHS7omsLyL4tXn05fTwCCC/r2yVpOaBE6a6omJfGsDf+ULVnCsazYSjMh6SLkpMVzMhT0vv@lists.postgresql.org X-Gm-Message-State: AOJu0Ywl11ugZUx1AelASy+Ds8v0moBu5EQxat5DxrTf8Gh1Nwc8CDpZ SaMuyJxIqsrPxPDoNJGMpgIfwArCpdLn16pcAsC8gzzOAIIgvCYL24rP5HauOZ9mueogaDoLfGl p X-Google-Smtp-Source: AGHT+IHbX5ig4oyeMVZIa+Hk2rZMUMa4I9KEaz78vLmJ4WEsea6tAqRKTl8h0kRcwiGdI+TX5Tr2OA== X-Received: by 2002:a05:600c:4f8e:b0:42c:b9c8:2bb0 with SMTP id 5b1f17b1804b1-4311dea3a6fmr33728305e9.4.1728709293225; Fri, 11 Oct 2024 22:01:33 -0700 (PDT) Received: from dynamic-pd01.res.v6.highway.a1.net ([2001:871:260:536:206a:2b5b:d652:a7f2]) by smtp.gmail.com with ESMTPSA id 5b1f17b1804b1-431182d7bddsm57322495e9.8.2024.10.11.22.01.32 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 11 Oct 2024 22:01:32 -0700 (PDT) Message-ID: <2c392993640661b817c5c779f6aaf44c103510bf.camel@cybertec.at> Subject: Re: Streaming Replication vs Logical From: Laurenz Albe To: Paul A Jungwirth , pgsql-docs@lists.postgresql.org Date: Sat, 12 Oct 2024 07:01:31 +0200 In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.4 (3.52.4-1.fc40) MIME-Version: 1.0 List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, 2024-10-11 at 15:53 -0700, Paul A Jungwirth wrote: > Our docs seem to contrast "streaming replication" to logical, but > these are not really opposites. Sometimes when they say "streaming" > they mean "physical". >=20 > Probably this is historical: at first physical replication was the > only kind of streaming we had. >=20 > Personally this has caused me a lot of confusion. For example, > recently when I read "Synchronous replication (see Section 26.2.8) is > only supported on replication slots used over the streaming > replication interface," I took it to mean synchronous replication only > worked for physical replication, not logical. What you are saying makes a lot of sense, and improving some of this is a good thing. Our current trminology is a mess. There are some places in the documentati= on that speak of physical vs. logical replication, while most places use the term "streaming replication" for physical replication. I myself consequent= ly speak of "streaming replication" vs. "logical replication", even though bot= h stream data. The protocol section of the documentation describes the "streaming replication protocol" and the "logical streaming replication pro= tocol". This is confusing, and I am also sometimes confused in the way you describe= d above. I think the mess is too well established to be really cleaned up. But addi= ng some clarity is a good thing, so +1. Yours, Laurenz Albe