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 1t6e26-00ETZ2-D6 for pgsql-docs@arkaria.postgresql.org; Thu, 31 Oct 2024 22:52:50 +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 1t6e23-006k65-KX for pgsql-docs@arkaria.postgresql.org; Thu, 31 Oct 2024 22:52:47 +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 1t6e23-006k4j-C1 for pgsql-docs@lists.postgresql.org; Thu, 31 Oct 2024 22:52:47 +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 1t6e1s-0044no-PH for pgsql-docs@lists.postgresql.org; Thu, 31 Oct 2024 22:52:46 +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=xiWD2T4MzW1qFkjaWjkYmv556P68jJ7bbDSGskqwQjQ=; b=abACdj6uD6oM8gKwiyGCaY4fKL okUZHNCe/OKMEPzKC4W+LkEkGqIvt/nP7rFv8gXNGmPXPy7R569l76w2mo5wMEruAc5/VyjhRRBHg hf6nTkCogzTvxJgrJT49mZBf1to7wzvl3Yq3zWM7cYuyS0xvZ7P6YZaE6ovNbYU9Hjj6v9JAbJYhE 1YAJiQE11VIgdS3BxnUMLStWwzq4WnYTTukdy8YkLOrf+Nf9MqKmE5cRM8Fhe/mBtLdcnQ/QfNxZc TOuEQiyAXqQuyuwf/8wn0qwPsLLDXWGWVoax6PyfuX87vyciSJB4hTWof3M49DH0c6FSY6VWB+O8s U5O4UCig==; Received: from bruce by momjian.us with local (Exim 4.96) (envelope-from ) id 1t6e1q-0040KT-04; Thu, 31 Oct 2024 18:52:34 -0400 Date: Thu, 31 Oct 2024 18:52:34 -0400 From: Bruce Momjian To: Peter Smith Cc: Koen De Groote , Laurenz Albe , pgsql-docs@lists.postgresql.org Subject: Re: Logical replication - initial data synchronization Message-ID: References: <81ac7c432d4c0559c6489b43fe6984c4c1ee1fd3.camel@cybertec.at> 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 Fri, Nov 1, 2024 at 09:07:38AM +1100, Peter Smith wrote: > On Fri, Nov 1, 2024 at 2:16 AM Bruce Momjian wrote: > > > > 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. > > > > One small nit -- I think "PostgreSQL" typically would have SGML markup: > > PostgreSQL Yes, I thought so too, but if you look at the SGML, it uses PostgreSQL with no markup in many places close to this sentence, e.g. "PostgreSQL supports both mechanisms concurrently". -- 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?"