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 1rklxz-00FE61-2x for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Mar 2024 14:21:55 +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 1rklxx-000W7F-JD for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Mar 2024 14:21:54 +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 1rklxw-000W77-GG for pgsql-hackers@lists.postgresql.org; Thu, 14 Mar 2024 14:21:53 +0000 Received: from fhigh4-smtp.messagingengine.com ([103.168.172.155]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rklxt-004Ule-ML for pgsql-hackers@postgresql.org; Thu, 14 Mar 2024 14:21:52 +0000 Received: from compute2.internal (compute2.nyi.internal [10.202.2.46]) by mailfhigh.nyi.internal (Postfix) with ESMTP id 43D6111400CF; Thu, 14 Mar 2024 10:21:48 -0400 (EDT) Received: from mailfrontend2 ([10.202.2.163]) by compute2.internal (MEProxy); Thu, 14 Mar 2024 10:21:48 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t=1710426108; x= 1710512508; bh=7fworkOr9cmb3JEv5VqQtO0Elag7iWYVVMR34iTSF5w=; b=p HxcdYHM1sKfTdc6rt8Q4iHJ4x7nASobQj8disAQd3TSEl6Y46ELOAw51vuKpvMvb RlIz8Vqh6dKD41Ia1ZLyeWw/0BhcIXx3r31ji3dIm6yJ63UQCIN5wNNfRhAluSty ICKMxx8+iqFKGasag1bX0Acp3khjGOZwrauFUKUGgmKIiwxcji1p35GTypZoFbPe Q5BTYBKv/imY8UXWDgyGfm/hwb//HalXpROrofzNuyQdL8cXIZRNM+2vez5cmfxW uiolreqavBH7x2PQFpPfM8GK35ayOHFxuMnpUODmOQNtgN47EChxVqKDpKEx+2XQ SxwUykUNRosaeWxYtCsiA== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrjeejgdeiudcutefuodetggdotefrodftvf curfhrohhfihhlvgemucfhrghsthforghilhdpqfgfvfdpuffrtefokffrpgfnqfghnecu uegrihhlohhuthemuceftddtnecusecvtfgvtghiphhivghnthhsucdlqddutddtmdenuc fjughrpeffhffvvefukfggtggugfgjsehtkeertddttdejnecuhfhrohhmpeetlhhvrghr ohcujfgvrhhrvghrrgcuoegrlhhvhhgvrhhrvgesrghlvhhhrdhnohdqihhprdhorhhgqe enucggtffrrghtthgvrhhnpedvkedtffduffdtffffheffhfejjefhgfeiueeukeejkeff gfdufffhudffffeuveenucffohhmrghinhepvghnthgvrhhprhhishgvuggsrdgtohhmne cuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmrghilhhfrhhomheprghlvhhh vghrrhgvsegrlhhvhhdrnhhoqdhiphdrohhrgh X-ME-Proxy: Feedback-ID: ia2694551:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Thu, 14 Mar 2024 10:21:47 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=alvh.no-ip.org; s=schmee; t=1710426106; bh=5+clcv6G5NWVy9+mzfaXwaWA+sAgNFq5w/yaqEQib0I=; h=Date:From:To:Cc:Subject:In-Reply-To:From; b=F56X8hJGkiKkS9KkXDcDLy1oMqReGtjMMbAFOteYhtPCnDE8ytJWaf0w24ypfxmYX 6vavNW6OcH//7T4RD8ZzQ1mR0J/L45XuhXVEobRF3dsuFkbpcEVyosvi15wQ5ifh65 xTjE2Bo/+sazZPCIpcnf/taE3MPSsSUfl8dQzutbCLupvY7ba1AlPTjSeHC0s7/w/H xMGiDj+LSitescb0gkOncBr97GQWtecCKctpouUD6ZbuEzPKrYDu5uOnjyYMURwTTt pPfSdeIXOEEMwiqPQo64reUYei286sHdK8mL+L3aFaJbK5kIAM85ssPRyQJKqCa6NM ZKxqQRL4iGDyg== Received: by schmee.alvh.no-ip.org (Postfix, from userid 1000) id 7B4F9CD5; Thu, 14 Mar 2024 15:21:46 +0100 (CET) Date: Thu, 14 Mar 2024 15:21:46 +0100 From: Alvaro Herrera To: Shlok Kyal Cc: Andrew Atkinson , Peter Smith , PostgreSQL-development Subject: Re: Add publisher and subscriber to glossary documentation. Message-ID: <202403141421.gkawed227diy@alvherre.pgsql> 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 2024-Mar-14, Shlok Kyal wrote: > Andrew Atkinson wrote: > > > Anyway, hopefully these examples show “node” and “database” are > > mixed and perhaps others agree using one consistently might help the > > goals of the docs. > > For me the existing content looks good, I felt let's keep it as it is > unless others feel differently. Actually it's these small terminology glitches that give me pause. If we're going to have terms that are interchangeable (in this case "node" and "database"), then they should be always interchangeable, not just in some unspecified cases. Maybe the idea of using "node" (which sounds like something that's instance-wide) is wrong for logical replication, which is necessarily something that happens database-locally. Then again, maybe defining "node" as something that exists at a database-local level when used in the context of logical replication is sufficient. In that case, it would be better to avoid defining it as a synonym of "instance". Then the terms are not always interchangeable, but it's clear when they are and when they aren't. "Node: in replication, each of the endpoints to which or from which data is replicated. In the context of physical replication, each node is an instance. In the context of logical replication, each node is a database". Does that make sense? I'd also look at altering "Primary" and "Standby" so that it's clearer that they're about physical replication, and don't mention "database" anymore, since that's the wrong level. Maybe turn them into "Primary (node)" and "Standby (node)" instead. -- Álvaro Herrera PostgreSQL Developer — https://www.EnterpriseDB.com/