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 1t1WfK-00GgVW-65 for pgsql-docs@arkaria.postgresql.org; Thu, 17 Oct 2024 20:00:10 +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 1t1WfH-009Kg6-Q4 for pgsql-docs@arkaria.postgresql.org; Thu, 17 Oct 2024 20:00:08 +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 1t1WfH-009Kfx-Hy for pgsql-docs@lists.postgresql.org; Thu, 17 Oct 2024 20:00:07 +0000 Received: from momjian.us ([72.94.173.45]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t1WfF-001atN-2t for pgsql-docs@lists.postgresql.org; Thu, 17 Oct 2024 20:00:07 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2024011501; h=In-Reply-To:Content-Transfer-Encoding:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Sender:Reply-To: Content-ID:Content-Description; bh=98Fuix1pmurQGC8sW4uKt10pJj39bRyeupW6VNXK4PA=; b=WcPpuiXrxYgtgmOIco5bE/j6/Q iCJikwJ/L9z8CYtVyQU/jUwXGnooPL7XFxhHbKYBOT3yFnK7qjKT56VAuvklhWwNm7NBY52VPgLE+ aUGA7wCZPRdZehvweu4XhUEbyzRu1ZGLdUxZHRTvRKzMChUCbGNMsQQrDgPnwZTRUWKpb1d+aNuml LZIHKSmGePUgtztxuVq1OhbcausWcbCJ9/Un7H0lubm5AcSMH2/wajOD/9OlojuGQpXU1eOXR+i5q BniNNOjshgYJazG01BzRpjGBBzSuhz9yNSXx25ArTYtvxJU74eEzr5ICDxISxXslyx3B00hTbp0Nq cmVUEjUw==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1t1WfD-002Reh-23; Thu, 17 Oct 2024 16:00:03 -0400 Date: Thu, 17 Oct 2024 16:00:03 -0400 From: Bruce Momjian To: Koen De Groote Cc: pgsql-docs@lists.postgresql.org Subject: Re: Logical replication - initial data synchronization Message-ID: References: <171606613152.686.7693963105919927503@wrigleys.postgresql.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Oct 17, 2024 at 09:57:04PM +0200, Koen De Groote wrote: > I would still add that the snapshot and data copying is handled by postgres > itself. That was the big question I was stuck with:"Who is taking this > snapshot? Do I have to do it? Will they explain how?" > > Because it's left in the middle who does it. Once you know how logical > replication works, it's obvious, re-reading the documentation I know what to > expect, but that's only because I've already done it a few time snow. > > As someone just starting and reading the documentation, it was a stumbling > block for me. > > To me, > > >   When logical replication of a table typically starts, a snapshot is > >   taken of the table's data on the publisher database and copied to the > >   subscriber > > Does not clarify that. > > It's the reason I created this mail: I would like it stated explicitly that the > database process takes care of this for us. Well, you are the first person to report this confusion, and we can't go around explaining what Postgres does and does not do in each section. I would need to hear from other people that this is confusing before making it explicit. -- 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?"