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.96) (envelope-from ) id 1vJy0p-00A840-2B for pgsql-committers@arkaria.postgresql.org; Fri, 14 Nov 2025 17:55:06 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.96) (envelope-from ) id 1vJy0n-007QZS-0d for pgsql-committers@arkaria.postgresql.org; Fri, 14 Nov 2025 17:55:05 +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.96) (envelope-from ) id 1vJy0m-007QZI-35 for pgsql-committers@lists.postgresql.org; Fri, 14 Nov 2025 17:55:04 +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.96) (envelope-from ) id 1vJy0k-007l1d-1f for pgsql-committers@lists.postgresql.org; Fri, 14 Nov 2025 17:55:04 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; 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=2M6hGpAeuZfUWhShhpEzQM2Mu/bMn3FQ/zrBF5orEx0=; b=FwIkv gqOvFOwL3BHbJhMrB6iOx0hKYmMu+iQvFa8g9r2OmaBGRVxD68r2752++YfZcr74mviqGbMztYA+4 stXI0cGygsUoYwwcK0ChAqcolwVDhkhCJO+jsSOQTPE2IoYDPYEQdfNGpX+zHUCiHxDcycOu4+qDZ IT/4ED9kqkxyZfdB28KbtazZ6rhNa1uEnxar1ChDIrBkgMzyVP4Chx3cXcnwXhvmUdytvmM9r/5gP WJoVpTTlxxZZ9qf692HThAv7+WcDiG9T6eAX5Nvscyq4x6w4FT37lFtdaVl9OxdYm1hSu4/Ur+sjL i+KWfuHlloR1OC6ODpx3N6ZG5z61A==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1vJy0i-0000000GkBp-33Kx; Fri, 14 Nov 2025 12:55:00 -0500 Date: Fri, 14 Nov 2025 12:55:00 -0500 From: Bruce Momjian To: Andres Freund Cc: pgsql-committers@lists.postgresql.org Subject: Re: pgsql: doc: remove verbiage about "receiving" data from rep. slots Message-ID: References: <53n63x724ahx2nwx42bmivjlt67fpbyh44knx7jazodsqcs5av@umzjyyg3clpq> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Fri, Nov 14, 2025 at 12:14:15PM -0500, Andres Freund wrote: > > Patch applied. I can keep improving it as we get more ideas. > > I'm rather baffled by the process here. You pushed a patch, without any > review, which also wasn't previously posted publicly, that made things > worse. Then, after you got pushback on that change, you posted another patch, > that got mildly negative feedback. Then you also pushed that change. Well, we talked privately on chat and I gave my reasons why I thought the additional detail was helpful. When you stopped replying, I thought that meant you were happy with the change, or had no ideas for improvement. Obviously my assumption was wrong. As I stated, I am open to continue improving it. To reiterate what I said on private chat, our only docs about replication slots are here: https://www.postgresql.org/docs/devel/warm-standby.html#STREAMING-REPLICATION-SLOTS It mostly talks about retaining WAL, and I cleaned that up to specify the cases where only physical replication was involved. (You can see yesterday's commits in the output.) Logical replication does more than just retain WAL, and since we were only referencing the above WAL-retention chapter from the subscription chapter: https://www.postgresql.org/docs/devel/warm-standby.html#STREAMING-REPLICATION-SLOTS I added a mention of "track relevant transaction activity". If that is wrong, what is the right wording that adds details beyond WAL retention? I personally was confused about replication slots, so I assumed these changes will help others. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.