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 1nenQ6-0001yS-7k for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Apr 2022 00:33:10 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nenQ4-0002mM-RU for pgsql-hackers@arkaria.postgresql.org; Thu, 14 Apr 2022 00:33:08 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nenQ4-0002mD-E2 for pgsql-hackers@lists.postgresql.org; Thu, 14 Apr 2022 00:33:08 +0000 Received: from mail-io1-xd2a.google.com ([2607:f8b0:4864:20::d2a]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nenQ0-0005Jx-4U for pgsql-hackers@postgresql.org; Thu, 14 Apr 2022 00:33:06 +0000 Received: by mail-io1-xd2a.google.com with SMTP id 125so3754693iov.10 for ; Wed, 13 Apr 2022 17:33:03 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20210112.gappssmtp.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=qaPMBYrVHKZNbI+1oFRkwcsloJQFStgl9Zj060eOhO8=; b=540vVvtFuks7iWbbo586cchs4NGJcDy/QvPG31Qr4scT5ATlENJWmrxibJ3YuTKA9N zdUOrCmcudBB49Blwr2yQHyVFpXckljw0om6BbG8+UUAEXS6O0H96fwFQeE7qqF60MzF RQBjlfrJvfuKDr1IKtSca9ploj0mOpv8JrMW8f9uLIVpBM1x+NX5n/v+ZkE/CrM3cIeS CX1O08NvbmKb3yCOq6LHGEHfCDOQHJXOsXpjj1C2RBQLWths8GbSiM4yoQ19XP5YsqOl 0Va4SRtvKmlS2MRIfxKDe8Dqn65SmHtSOqy0ZRhKV7GBU/YOVYXAqTz7WykxFf0vPr+V rXIw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=qaPMBYrVHKZNbI+1oFRkwcsloJQFStgl9Zj060eOhO8=; b=D89YMFHE98y87QMhl6u57GbTmwUnwiityHTkAKA+pgEGINtPMZAK2jE6TYqJv3FdAg 9cdOuYmxk/wpMuLSzwxg3cZg00nauc9bs/kznWF98nkgmQYog0lhmwBTg+RKjwCVu9ko VYJOw8i/yN8tfN/8Ro2d+vjTFghNYu52LdyrLUgRZt84PpXJr67paXbZSphPiziRx2no Gf91oGm0EpHlfDPCFE7ABXaT4hRhrfPbGnxQIRTK5Fz1nChk4BsiM7NNjEKX7GMACOyi OCLcwYeNR8R8fkuTa3oEaZVe728U2S7E8blAC0RdVfil0JZWK81eFdpFY+e2lpYtKtRL 06tw== X-Gm-Message-State: AOAM5328Pilw44Pv7S5gSKNslbRbcboDL+SG5a1aBuh7mg4m9L5eRPL0 IOcFMYoyweSRTGrNmitMquc8VA== X-Google-Smtp-Source: ABdhPJxnDTpdveVYN7V4nTzTndZ1r9Bg+6PrQnS/B85r5OsxobUiyrAmM2EGAkq7EuYIdbY8U7Vh3w== X-Received: by 2002:a05:6638:38a3:b0:326:24b9:e196 with SMTP id b35-20020a05663838a300b0032624b9e196mr46904jav.255.1649896383347; Wed, 13 Apr 2022 17:33:03 -0700 (PDT) Received: from pryzbyj.telsasoft (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id a2-20020a5d9ec2000000b00645ab33390dsm273641ioe.9.2022.04.13.17.33.02 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Wed, 13 Apr 2022 17:33:02 -0700 (PDT) Received: by pryzbyj.telsasoft (Postfix, from userid 1000) id 0DF2C80140C; Wed, 13 Apr 2022 19:33:02 -0500 (CDT) Date: Wed, 13 Apr 2022 19:33:01 -0500 From: Justin Pryzby To: David Rowley Cc: Alvaro Herrera , pgsql-hackers@postgresql.org, Fabien COELHO Subject: Re: typos Message-ID: <20220414003301.GT26620@telsasoft.com> References: <202204131729.g27uwttzzgao@alvherre.pgsql> <20220413174056.GQ26620@telsasoft.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Thu, Apr 14, 2022 at 09:39:42AM +1200, David Rowley wrote: > On Thu, 14 Apr 2022 at 05:40, Justin Pryzby wrote: > > There's (only) a few remaining. > > I've pushed 0001 and 0002 of the 3rd batch of patches. I left 0003 as Thanks > I just didn't feel it was a meaningful enough improvement. > > From docs/, if I do: > > $ git grep ", which is the default" | wc -l > 9 > > $ git grep ", the default" | wc -l > 64 > > You're proposing to make the score 10, 63. I'm not sure if that's a > good direction to go in. Well, I'm proposing to change the only instance of this: $ git grep -F ", the default)" doc/src/sgml/ref/create_publication.sgml: partition's row filter (if the parameter is false, the default) or the root Maybe what's needed is more like this. If the publication contains a partitioned table, and the publication parameter publish_via_partition_root is false (the default), then the row filter is taken from the partition; otherwise, the row filter is taken from the root partitioned table. I'll plan to keep this around and may come back to it later. On Thu, Apr 14, 2022 at 08:56:22AM +1200, David Rowley wrote: > I've left out the following change as it does not seem to be bringing > any sort of consistency to the docs overall. It only brings > consistency to a single source file in the docs. > > - You need zstd, if you want to support > + You need ZSTD, if you want to support > > See: git grep -i ">zstd<" It may not be worth changing just this one line, but the reason I included it here is for consistency: $ git grep 'zstd.*product' doc doc/src/sgml/config.sgml: zstd (if PostgreSQL $ git grep 'ZSTD.*product' doc doc/src/sgml/install-windows.sgml: ZSTD doc/src/sgml/install-windows.sgml: Required for supporting ZSTD compression doc/src/sgml/installation.sgml: You need ZSTD, if you want to support doc/src/sgml/installation.sgml: Build with ZSTD compression support. If we were to change it, maybe they should all say "Zstandard (zstd)". ZSTD looks like an acronym, which I think it is not, and Zstandard indicates how to pronounce it.