Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmFMp-00074P-Gd for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Apr 2023 14:53:07 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pmFMo-0000mE-7o for pgsql-hackers@arkaria.postgresql.org; Tue, 11 Apr 2023 14:53:06 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1pmFMn-0000m5-Uu for pgsql-hackers@lists.postgresql.org; Tue, 11 Apr 2023 14:53:05 +0000 Received: from mail-il1-x133.google.com ([2607:f8b0:4864:20::133]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pmFMl-002FfT-FZ for pgsql-hackers@lists.postgresql.org; Tue, 11 Apr 2023 14:53:05 +0000 Received: by mail-il1-x133.google.com with SMTP id t5so16143462ilu.5 for ; Tue, 11 Apr 2023 07:53:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; t=1681224781; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=vJ+x7AM4643Bxu6Xbbv1+iVuDqMelSp6y7+PBTRMqNo=; b=Z8xC/YUknjwOOY9hg9pQ05F2rp+sOxZFhxhAlU/bPdOWPBGYGKVEF+hHVBFi01dqEb WZKfjDF9uBzNtnic0fPPo0HGzmoQYIlsPGuS36HPkyHYR7DzdQNO4JjpTW3exW0Kv9WN 7ymE4tV7SleYaAKbLruZNIneXvgUY9CbgHfHSyAaDn6rreqGlt3GklJ+poYZc8oIHgWD swevRvMSpk+kXZ6tlph8pRLLUpiSVOCka0+awagK/evb8/39YXjKQ03gIpNzgokpwnW4 9A6GpIlf3Jz4uIt2Z9+D/ddbAVmQfvYW227/TA3d0UO1/lf43hEOKRQzm7IBj6fOWx/7 k1kQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681224781; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=vJ+x7AM4643Bxu6Xbbv1+iVuDqMelSp6y7+PBTRMqNo=; b=jIQGK8oxdiAIeVECM733GP0JeGhc9UdRdLfncikMAA0rPdlBonslXkPE7quUiMmpQ4 xPPgjlAy5L2IdqkKYIhtcvawW/LuBZnLSUNSdX6P6M/AqY3jO+0tZ/vBO8TCH8RPqWEV FCm43uZY3i3d9Lko00XSTclZeHAd/N+2U1S+Q7tvOLxYWzDl2/U6UUui2H+9chUh2RH9 /Yn6NqNbi8DhQnR+D+++vaKJU1S0AotE7dXORPPVrKNKIVbh2aO2WG6fQvW9a4MIFuzP nbQ3OArJ0mFobZn3myple+Vt1ieW1faZ620eHuZZBxEHtPaJOx5yKbA20LbEk7NVSXy2 NrhA== X-Gm-Message-State: AAQBX9dkGE0IoZKYlk/noQ8ixnm2WBuvh6b1j4ufLto4LigMeMoB2GZr pyCBucy0cINhVEiIDqkhBk6YXg== X-Google-Smtp-Source: AKy350YYDg/lxq9tyFjSpBapN1nY3dH20WYmtDLhLSZGs+2IHC8W7VEMTdvXn0GwQKKG841RT5ActQ== X-Received: by 2002:a92:c52c:0:b0:328:a7bc:b42e with SMTP id m12-20020a92c52c000000b00328a7bcb42emr1336802ili.21.1681224781680; Tue, 11 Apr 2023 07:53:01 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id j9-20020a922009000000b003287961ce81sm2448601ile.50.2023.04.11.07.53.01 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Apr 2023 07:53:01 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 40BC0800966; Tue, 11 Apr 2023 09:53:00 -0500 (CDT) Date: Tue, 11 Apr 2023 09:53:00 -0500 From: Justin Pryzby To: Thom Brown Cc: pgsql-hackers@lists.postgresql.org Subject: Re: Various typo fixes Message-ID: References: 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 Tue, Apr 11, 2023 at 03:43:12PM +0100, Thom Brown wrote: > On Tue, 11 Apr 2023 at 15:39, Justin Pryzby wrote: > > > > On Tue, Apr 11, 2023 at 03:36:02PM +0100, Thom Brown wrote: > > > I've attached a patch with a few typo and grammatical fixes. > > > > I think you actually sent the "git-diff" manpage :( > > Oh dear, well that's a first. Thanks for pointing out. Thanks. I think these are all new in v16, right ? I noticed some of these too - I'll send a patch pretty soon. |+++ b/doc/src/sgml/logicaldecoding.sgml |@@ -326,11 +326,11 @@ postgres=# select * from pg_logical_slot_get_changes('regression_slot', NULL, NU | connection is alive (for example a node restart would break it). Then, the | primary may delete system catalog rows that could be needed by the logical | decoding on the standby (as it does not know about the catalog_xmin on the |- standby). Existing logical slots on standby also get invalidated if wal_level |- on primary is reduced to less than 'logical'. This is done as soon as the |- standby detects such a change in the WAL stream. It means, that for walsenders |- that are lagging (if any), some WAL records up to the wal_level parameter change |- on the primary won't be decoded. |+ standby). Existing logical slots on standby also get invalidated if |+ wal_level on the primary is reduced to less than 'logical'. |+ This is done as soon as the standby detects such a change in the WAL stream. |+ It means that, for walsenders which are lagging (if any), some WAL records up |+ to the wal_level parameter change on the primary won't be decoded. | I think "logical" should be a here.