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 1t4Eoe-00H7Tp-As for pgsql-docs@arkaria.postgresql.org; Fri, 25 Oct 2024 07:33:00 +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 1t4Eoc-00DfMj-I4 for pgsql-docs@arkaria.postgresql.org; Fri, 25 Oct 2024 07:32:58 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t4Eoc-00DfMb-9g for pgsql-docs@lists.postgresql.org; Fri, 25 Oct 2024 07:32:58 +0000 Received: from mail-ed1-x531.google.com ([2a00:1450:4864:20::531]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t4EoW-002sO8-KC for pgsql-docs@lists.postgresql.org; Fri, 25 Oct 2024 07:32:57 +0000 Received: by mail-ed1-x531.google.com with SMTP id 4fb4d7f45d1cf-5c903f5bd0eso3216890a12.3 for ; Fri, 25 Oct 2024 00:32:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cybertec.at; s=cybertec.at; t=1729841571; x=1730446371; darn=lists.postgresql.org; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:from:to:cc:subject :date:message-id:reply-to; bh=MmtQS0ix6tQAdkRVmvm2nPbovyV1rSL7zKYmBVeOi4c=; b=Ss5YIBAX4GGH0DmPOMsJb90l8Q9WxcRmvZs+wKlFEtNX2p9/8fLBgqRpwMbZfwBO7v cCEfRB0x4ByC8eDCxN9BTS7dz0dPdEwDi46/5TY0JVrFbCgd7cjelwmLqQdqjqdbSx4p OE2kwAdVzHDE/0AKoozo9Src9WembSOgBcp3A= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729841571; x=1730446371; h=mime-version:user-agent:content-transfer-encoding:references :in-reply-to:date:cc:to:from:subject:message-id:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=MmtQS0ix6tQAdkRVmvm2nPbovyV1rSL7zKYmBVeOi4c=; b=YLBEsG5AvCQKJ0MSNg/wplesrKdIpHcQlF9V/GSEs6LMEWOETz+KWHYa0uRBigQQaZ 0sZQOnaySaT6oLNt8xE8a5jDHDwG4xW3NnPtLA7R6dF1C11lBR2d8QameUWk8uh3KHCm PAYnB9wIlytCtL3u7/brGhR9yNpC6BVqLAWc6XCCv3uCX4FoOegJpygGkAc5yvhJUT3G 521s3OqZQf/oycPfiZ1kgzx3kOmELOwr59XWejldT5kgDN/shi7RxOMeXyji81S815RT +VLQnCDItEKcPgMCfiKhRrQ2kTgh6IFR4fgfu3pyb2NDTcdq2iAV3RwsABpMd034JJWG zPjA== X-Forwarded-Encrypted: i=1; AJvYcCXtxE3Bd31nPZdg2CMpqHaocn50a2Z9Znfbp8iSgPavhcBzGlXrMh2gNli97+k95c6SRmro2SDxYo5X@lists.postgresql.org X-Gm-Message-State: AOJu0Yy4oVy0WMktPoWZwyzn29F6vmYLCdwm79hLwWMCr8269brYkxnW KkupqlNkuqA81cSY02A5NFYcoVQDq2ZdI2GXeyXkEBdXQpRbGcjrraihNrkS9EU= X-Google-Smtp-Source: AGHT+IEImwUdIYv8xbY4CmvzlYtXUKmX44nlNtavLmED36ikPY8IAhDD298NNSGmlUmq8K9X3vu+IQ== X-Received: by 2002:a17:907:7296:b0:a9a:2afc:e4d9 with SMTP id a640c23a62f3a-a9abf8a1170mr812011766b.29.1729841571452; Fri, 25 Oct 2024 00:32:51 -0700 (PDT) Received: from localhost.localdomain (86.73.73.85.static.otenet.gr. [85.73.73.86]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a9b1e0b23b2sm37743966b.4.2024.10.25.00.32.50 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Fri, 25 Oct 2024 00:32:51 -0700 (PDT) Message-ID: Subject: Re: Logical replication - initial data synchronization From: Laurenz Albe To: Peter Smith Cc: Bruce Momjian , Koen De Groote , pgsql-docs@lists.postgresql.org Date: Fri, 25 Oct 2024 10:32:49 +0300 In-Reply-To: References: <171606613152.686.7693963105919927503@wrigleys.postgresql.org> <81ac7c432d4c0559c6489b43fe6984c4c1ee1fd3.camel@cybertec.at> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.52.4 (3.52.4-2.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-25 at 17:22 +1100, Peter Smith wrote: > It seems to me the same clarification could be achieved just by adding > 1 word ("PostgreSQL") to the original text. e.g. >=20 > BEFORE > Logical replication of a table typically starts with taking a snapshot > of the data on the publisher database and copying that to the > subscriber. >=20 > AFTER #1 (I added "PostgreSQL") > Logical replication of a table typically starts with PostgreSQL taking > a snapshot of the data on the publisher database and copying that to > the subscriber. +1 on this version. Either this way or the way I suggested, it doesn't matter as far as I am concerned. Perhaps Koen wants to chime in and say what sounds best to him. > Or, AFTER #2 (I added "PostgreSQL internally") > Logical replication of a table typically starts with PostgreSQL > internally taking a snapshot of the data on the publisher database and > copying that to the subscriber. Yours, Laurenz Albe