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 1q6uv9-0006H8-QT for pgsql-docs@arkaria.postgresql.org; Wed, 07 Jun 2023 15:17:59 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1q6uv8-0007Eo-NM for pgsql-docs@arkaria.postgresql.org; Wed, 07 Jun 2023 15:17:58 +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 1q6uv8-0007Az-Eq for pgsql-docs@lists.postgresql.org; Wed, 07 Jun 2023 15:17:58 +0000 Received: from new1-smtp.messagingengine.com ([66.111.4.221]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1q6uv2-000jCV-2C for pgsql-docs@lists.postgresql.org; Wed, 07 Jun 2023 15:17:54 +0000 Received: from compute4.internal (compute4.nyi.internal [10.202.2.44]) by mailnew.nyi.internal (Postfix) with ESMTP id E39325800E7; Wed, 7 Jun 2023 11:17:50 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute4.internal (MEProxy); Wed, 07 Jun 2023 11:17:50 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:cc:content-transfer-encoding :content-type:content-type:date:date:feedback-id:feedback-id :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:sender:subject:subject:to:to:x-me-proxy :x-me-proxy:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; t= 1686151070; x=1686158270; bh=GdFg/RaQibK80onkCIdUdM1Pq8jID5UGvMC Nd/0NliI=; b=tUCpsbQAaL/JwQ7gQjtJH1RH5dlEr+56iOqqpK4AfIHc9nWcuSC 90r4Yq1/kWJPF1R9gVOEi4wRuTaXhLPRtRpCCm0pO3OKPe7EgKA9rnAq65HsOPol QgL2vT3KUXSGkOGFBFXXkBCQx9XT0XesZqUHM9VjbpBWwFVRQTsnhBQWIfLDc+P7 Y1I8VKn8bTxQhPa3nCQCrbVVoxbxjaMya26KG0UCTD1gjYZArgPpMjtl14Cxu30H 0lq342Hms4mgI0IXiAqqFOIYeH13t5ibgtS7Pc/Sjs7CC38YCY1caUBaroz2Ful3 eRP78TBdI+OMkfwNj6A/Xmey7OhQ+4M2Eqg== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvhedrgedtgedgkeeiucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucesvcftvggtihhpihgvnhhtshculddquddttddmne cujfgurhepkfffgggfuffvvehfhfgjtgfgsehtkeertddtfeejnecuhfhrohhmpefrvght vghrucfgihhsvghnthhrrghuthcuoehpvghtvghrrdgvihhsvghnthhrrghuthesvghnth gvrhhprhhishgvuggsrdgtohhmqeenucggtffrrghtthgvrhhnpefhjeduueelfeehuedt udefteejveegieeiueejueehfeektddtueeiieeitefhveenucevlhhushhtvghrufhiii gvpedtnecurfgrrhgrmhepmhgrihhlfhhrohhmpehpvghtvghrrdgvihhsvghnthhrrghu thesvghnthgvrhhprhhishgvuggsrdgtohhm X-ME-Proxy: Feedback-ID: i131946ab:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Wed, 7 Jun 2023 11:17:48 -0400 (EDT) Message-ID: Date: Wed, 7 Jun 2023 17:17:47 +0200 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:102.0) Gecko/20100101 Thunderbird/102.11.0 Subject: Re: confusing positioning of notes in connection settings Content-Language: en-US To: "Jonathan S. Katz" , Daniel Gustafsson Cc: Pg Docs References: <6f825d42-a1ce-492a-2ea7-c83e6e65fa8b@postgresql.org> <4e34fcb4-6791-0266-7352-27b769c478f9@enterprisedb.com> <39202431-DF62-42E2-B0C1-500C93AD37C8@yesql.se> <739043ea-9fe8-3fa5-ed10-aa988eaeb121@postgresql.org> From: Peter Eisentraut In-Reply-To: <739043ea-9fe8-3fa5-ed10-aa988eaeb121@postgresql.org> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 05.06.23 19:10, Jonathan S. Katz wrote: > On 5/31/23 7:53 AM, Daniel Gustafsson wrote: >>> On 31 May 2023, at 13:16, Peter Eisentraut >>> wrote: >> >>> The first two hunks are pretty straightforward, they just move the >>> existing text around. >>> >>> For the other two, which are not supported on Windows, I added an >>> explicit parenthetical note.  We don't list which of the Unix-like >>> platforms support the respective options, but I suspect that it's all >>> of them in practice?  (Otherwise we should be more explicit.)  So I >>> think calling out Windows explicitly is sensible, also considering >>> that the first two settings are supported on Windows but the latter >>> two are not. >> >> I think this is a clear improvement over the current docs. > > +1. > > Small nit: > > "which does not include Windows" => > "which is not supported on Windows" > > (in two places) The proposed text in the patch is "This parameter is supported only on systems that {have this property} (which does not include Windows)." I don't see how the change you are proposing is correct.