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 1t6Wui-00DbbW-3q for pgsql-docs@arkaria.postgresql.org; Thu, 31 Oct 2024 15:16:44 +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 1t6Wug-002LiO-9i for pgsql-docs@arkaria.postgresql.org; Thu, 31 Oct 2024 15:16:42 +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 1t6Wug-002Li5-1b for pgsql-docs@lists.postgresql.org; Thu, 31 Oct 2024 15:16:42 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t6Wud-003npW-Ib for pgsql-docs@lists.postgresql.org; Thu, 31 Oct 2024 15:16:41 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=BGeLNLFbk+SJ8zV30DnYTvq2mcgjJQh5WE1XeDZFtvU=; b=FgemS UwyDCUiKvzIPNWwT3DOKGqyiLWU+7PB9dI2Nh6YX9IEgfAM+xcWNukcIQUbYrXqdf/4OORywngkIn nWc9tcBwSdsXJ6aBF+P07XWP/1biEtyVHLZY53XrAn++mKpnj5UOQZNY7mN+QuP9fOhNyDUfgSKCN 8lAVDE/CBf/WzXrVrj99u3aNl1PQsAzio7Zn9oGH+DdvZFt0lGJBVAnhR7qtj96nvZV/XDbo448OT 3EyX+5ADB5Vm93k2eIXW5fNtXdeDlcq/zMyUGwrqZKjD4NtxgaLkgoC5lA9doUMw2tubOPWFevsL8 ilynCBfbi6/7aE9gAFCeBkWOyzWCw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1t6Wua-003DiF-2q; Thu, 31 Oct 2024 11:16:36 -0400 Date: Thu, 31 Oct 2024 11:16:36 -0400 From: Bruce Momjian To: Koen De Groote Cc: Laurenz Albe , Peter Smith , pgsql-docs@lists.postgresql.org Subject: Re: Logical replication - initial data synchronization Message-ID: References: <171606613152.686.7693963105919927503@wrigleys.postgresql.org> <81ac7c432d4c0559c6489b43fe6984c4c1ee1fd3.camel@cybertec.at> MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="pcNnFxWfUwNcvpxe" Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --pcNnFxWfUwNcvpxe Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Fri, Oct 25, 2024 at 11:48:16PM +0200, Koen De Groote wrote: > Number 2 would be perfect, I think. It leaves no doubt at all. I went with even more direct wording, patch attached. Glad we could improve this together --- the feedback from everyone was helpful. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com When a patient asks the doctor, "Am I going to die?", he means "Am I going to die soon?" --pcNnFxWfUwNcvpxe Content-Type: text/x-diff; charset=us-ascii Content-Disposition: attachment; filename="logical.diff" diff --git a/doc/src/sgml/logical-replication.sgml b/doc/src/sgml/logical-replication.sgml index 98a7ad0c272..111cc51f504 100644 --- a/doc/src/sgml/logical-replication.sgml +++ b/doc/src/sgml/logical-replication.sgml @@ -24,10 +24,11 @@ - Logical replication of a table typically starts with taking a snapshot - of the data on the publisher database and copying that to the subscriber. - Once that is done, the changes on the publisher are sent to the subscriber - as they occur in real-time. The subscriber applies the data in the same + When logical replication of a table typically starts, PostgreSQL takes + a snapshot of the table's data on the publisher database and copies it + to the subscriber. Once complete, changes on the publisher since the + initial copy are sent continually to the subscriber. The subscriber + applies the data in the same order as the publisher so that transactional consistency is guaranteed for publications within a single subscription. This method of data replication is sometimes referred to as transactional replication. @@ -165,7 +166,7 @@ The individual tables can be added and removed dynamically using ALTER PUBLICATION. Both the ADD TABLE and DROP TABLE operations are - transactional; so the table will start or stop replicating at the correct + transactional, so the table will start or stop replicating at the correct snapshot once the transaction has committed. @@ -1952,15 +1953,6 @@ CONTEXT: processing remote data for replication origin "pg_16395" during "INSER Architecture - - Logical replication starts by copying a snapshot of the data on the - publisher database. Once that is done, changes on the publisher are sent - to the subscriber as they occur in real time. The subscriber applies data - in the order in which commits were made on the publisher so that - transactional consistency is guaranteed for the publications within any - single subscription. - - Logical replication is built with an architecture similar to physical streaming replication (see ). It is --pcNnFxWfUwNcvpxe--