Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKDWL-0001vI-RG for pgsql-hackers@arkaria.postgresql.org; Sat, 27 Apr 2019 02:56:58 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.89) (envelope-from ) id 1hKDWK-0006Pq-8i for pgsql-hackers@arkaria.postgresql.org; Sat, 27 Apr 2019 02:56:56 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKDWJ-0006Da-Nw for pgsql-hackers@lists.postgresql.org; Sat, 27 Apr 2019 02:56:55 +0000 Received: from mail-it1-x12b.google.com ([2607:f8b0:4864:20::12b]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_CBC_SHA1:256) (Exim 4.89) (envelope-from ) id 1hKDWG-0001Ut-V5 for pgsql-hackers@postgresql.org; Sat, 27 Apr 2019 02:56:55 +0000 Received: by mail-it1-x12b.google.com with SMTP id s3so8879641itk.1 for ; Fri, 26 Apr 2019 19:56:52 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=telsasoft-com.20150623.gappssmtp.com; s=20150623; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to:user-agent; bh=Te5iGyKNB8KN43WbOjI+bKcxUc2QboLmXT2gImimGTE=; b=liRQbtv+s/I8ctktWDfgwohTJFWBymeGt9tfiLQ2C+5mtLLHC3Cxm2q61pAi0HjuL5 JWJDu3yRMdBRXqneaLd6SKN9rwBjIUnhE/D7H2Vi0Qf0qOwu2R52TeKAzKb7W9+CPA1v Z8ByCozm60iP6tJtvVTWXEd1o0BGLlaGH5YpmDs/+4bZUjWa5fUvX078PEDAOCOUeHeh hdBSyQHt3FGLdWDbaGv9USdYYKNYWQL5GKhKUpL2MqhJklhHdHO3lwOKDmDfCsZomRyj +XH85drDlM/UCu1yKsec08hWSS7CnCaym3dK4hkSU27MvOCPm3x5WgMvLAv0nYERL0+X 3EXA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to:user-agent; bh=Te5iGyKNB8KN43WbOjI+bKcxUc2QboLmXT2gImimGTE=; b=uEevDWOycaIya9vdzj/oecTXH+Y7q5VwIAMb2jY0fYPA8axeqUmwyyLjsz297p6yui XsiQiEG8ks2tXexc/FoQG5WXipVgHmjzXYRl5yeABHupeQhb5qo6Ry7Wm3x5QR5YniDu W9KL9PRKRTuT5vq0H2c5djFnmuCdtS8Gvfx8iI4YmyGp2iHWpu9uCh8yHBconkpBCXQB nRe8RiHPwA4mDmsvOSVWmOy4tPvrdNg2sOeK/ggXoG9aIKJCrIZ2GtdEoDJ9Q+EGrM9P SiMKRomzkvVVi0+wqfj/h6vFFzICyt/oM5LS6ThskMv+2h/i47YwnBCP9wg5p4IzkTfJ xLIg== X-Gm-Message-State: APjAAAXHYRlUlv7D+D9ZgBeCIDzd0/lv1Q68XBQIkepSuvyuRnaYrTjD 2hsaLNyJmKoY2SEF9EffmqUhfA== X-Google-Smtp-Source: APXvYqxilJ7bKr4seDkSdJhzOdVhmn9JQjokwk8etYaM/VpqDGTMoizYnsKhsXjtA2rr2gHbW+q3+A== X-Received: by 2002:a24:424c:: with SMTP id i73mr11159220itb.91.1556333810291; Fri, 26 Apr 2019 19:56:50 -0700 (PDT) Received: from pryzbyj (charmander.telsasoft.com. [50.244.222.1]) by smtp.gmail.com with ESMTPSA id n26sm8837441iog.23.2019.04.26.19.56.48 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Fri, 26 Apr 2019 19:56:49 -0700 (PDT) Received: by pryzbyj (Postfix, from userid 1000) id D80E280091E; Fri, 26 Apr 2019 21:56:47 -0500 (CDT) Date: Fri, 26 Apr 2019 21:56:47 -0500 From: Justin Pryzby To: Michael Paquier Cc: Alvaro Herrera , Andres Freund , pgsql-hackers@postgresql.org Subject: Re: clean up docs for v12 Message-ID: <20190427025647.GD3925@telsasoft.com> References: <20190422160807.xmdhtrtpowkjmyfd@alap3.anarazel.de> <20190422161955.GA17411@alvherre.pgsql> <20190423025042.GI2712@paquier.xyz> <20190426171722.GB3925@telsasoft.com> <20190427004420.GD2032@paquier.xyz> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190427004420.GD2032@paquier.xyz> User-Agent: Mutt/1.5.24 (2015-08-30) List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk On Sat, Apr 27, 2019 at 09:44:20AM +0900, Michael Paquier wrote: > On Fri, Apr 26, 2019 at 12:17:22PM -0500, Justin Pryzby wrote: > > But I think the biggest part of the patch is still not even reviewed ? > > I'm referring to ./*review-docs-for-pg12dev.patch > > Nope. I looked at the patch, and as mentioned upthread the suggested > changes did not seem like improvements as the existing sentences make > sense, at least to me. Do you have any particular part of your patch > where you think your wording is an improvement? Why do you think so? That's mostly new language from v12 commits which I specifically reviewed and worth cleaning up before release. If nobody else is interested then I'll forget about it, but they're *all* (minor) improvements IMO. I don't think it's be useful to enumerate justifications for each hunk; if one of them isn't agreed to be an improvement, I'd just remove it. But here's some one-liner excerpts. - is 2 bits and maximum is 4095. Parameters for + is 2 bits and the maximum is 4095. Parameters for Adding "the" makes it a complete sentence and not a fragment. - all autovacuum actions. Minus-one (the default) disables logging + all autovacuum actions. -1 (the default) disables logging There's nothing else that says "minus-one" anywhere else on that page. I just found one in auto-explain.sgml, which I changed. - than 16KB; gss_wrap_size_limit() should be used by the + than 16kB; gss_wrap_size_limit() should be used by the Every other use in documentation has a lowercase "kay", and PG itself doesn't accept "KB" unit suffix. - A few features included in the C99 standard are, at this time, not be + A few features included in the C99 standard are, at this time, not permitted to be used in core PostgreSQL Indisputably wrong ? Justin