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 1pmRPg-0003Rm-Dz for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Apr 2023 03:44:52 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1pmRPe-0002Hy-Q9 for pgsql-hackers@arkaria.postgresql.org; Wed, 12 Apr 2023 03:44:50 +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 1pmRPe-0002Fi-DY for pgsql-hackers@lists.postgresql.org; Wed, 12 Apr 2023 03:44:50 +0000 Received: from mail-io1-xd31.google.com ([2607:f8b0:4864:20::d31]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1pmRPb-002Mbr-MQ for pgsql-hackers@lists.postgresql.org; Wed, 12 Apr 2023 03:44:49 +0000 Received: by mail-io1-xd31.google.com with SMTP id n1so521629ioz.0 for ; Tue, 11 Apr 2023 20:44:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; t=1681271085; x=1683863085; 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=tio5njttumcqOvxy9IUw88NT7v9+0YQTpADOFryVCi8=; b=qRrqZYzVOaXda8+1Usn9sS17uSp7/2nVFuTpvbnruYxfyh7PMcb5qJi39XRcjpebmh N3R4Ym1Zk+Phc21peaoVafmnd5bBugi6+l7BnhGHo2rWan90r17mpmItdbhKiCQTrygP K2aqQWDuDIVcKhz0GsSNIz0iT39YOxNKTIajZDlg/v9+QJbeDzaI/XScWuIprWBKNVss uz6T2htGpRemRrt/Zh26TzN+dIfK03VIvn5Uvb4LSgIAekaH+jVENN9r5THmxINcaNv1 mpFJEGMIULzRU0FYr6Vra6gZaci/y1G9YD93msk5BToJZIFaFYsV9Skx7pGmHdUtDczp CjKQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1681271085; x=1683863085; 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=tio5njttumcqOvxy9IUw88NT7v9+0YQTpADOFryVCi8=; b=J6f1WAAB0ztXHx7KFVI1EaZTE5khp7c3pikEVxN9ivVHqU1nMXtxHchJqHZ3m0oAjl sUwlEQhE42ScxSXA5QLYn/YeBmQmAPKc5TkI7KD2EPUZH3uhGMMvvim6wU9BwP08/NgE kK6wLQWxoH8xHIZf9JPT+tx4kF9qPR87mq/Si+93rXiRLZecud+b1NCYX19ODDbYTgfz Qsh1mWjpY4cKtFLHybiO/sQZ1iosQb7icTU7KilFwjNdCpoDzSZ+EX//N7Hi2wrvBx6+ 6o0k8BQ7qmir1hOAc0vFyN/YXO9giOHLjpTsChWTEMNaDh9v7DOGeEQbN+7xYkrLBctt mZBw== X-Gm-Message-State: AAQBX9e6aCw6bCXXxmpAsUYfkb1QyFF9tTlXxHfP8DAfU+JWW2fjFEdP IFUhBl3MIxOdhBJeGiOL39nPmg== X-Google-Smtp-Source: AKy350YWw2EnWNAycnetNsG1xzdPQbFpxWFgaO6yUtoWRiO7v1DJ4vlkAknuMhENKv6+TM9Jc2n4Pw== X-Received: by 2002:a5d:8049:0:b0:755:7b0c:6042 with SMTP id b9-20020a5d8049000000b007557b0c6042mr8529954ior.2.1681271085579; Tue, 11 Apr 2023 20:44:45 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id t13-20020a5e990d000000b0075b3caacc6dsm4126452ioj.55.2023.04.11.20.44.44 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 11 Apr 2023 20:44:44 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 15C4B801BB2; Tue, 11 Apr 2023 22:44:44 -0500 (CDT) Date: Tue, 11 Apr 2023 22:44:43 -0500 From: Justin Pryzby To: Michael Paquier Cc: Daniel Gustafsson , Thom Brown , 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 Wed, Apr 12, 2023 at 12:28:25PM +0900, Michael Paquier wrote: > On Tue, Apr 11, 2023 at 11:12:58PM +0200, Daniel Gustafsson wrote: > > > On 11 Apr 2023, at 16:53, Justin Pryzby wrote: > > > > > I think "logical" should be a here. > > > > Agree, it should in order to be consistent. > > Indeed. > > + to the wal_level parameter change on the primary won't be decoded. > > This wal_level should also have a markup. > > Number of uses of logical slots in this database that have been > - canceled due to old snapshots or a too low > + canceled due to old snapshots or too low a > > This sounds a bit strange to me. A too low wal_level would be a cause > for a cancel, hence shouldn't this be "canceled due to old snapshots > or due to a too low guc-wal-level? That's the same as the original language which Thom and I are requesting to change, (but you added another "due to"). "a too low" is poor english. It's good enough for a code comment, but this is a user-facing doc. It could be "an inadequate wal-level" or "a prohibitively low wal-level", but Thom's language is better. "too low a wal-level" means the same thing as "too low of a wal-level" (which would also be fine). -- Justin