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 1jYenp-0003mv-HX for pgsql-docs@arkaria.postgresql.org; Tue, 12 May 2020 23:59:13 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1jYeno-0001Z1-9f for pgsql-docs@arkaria.postgresql.org; Tue, 12 May 2020 23:59:12 +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 1jYeno-0001Yt-3m for pgsql-docs@lists.postgresql.org; Tue, 12 May 2020 23:59:12 +0000 Received: from sss.pgh.pa.us ([66.207.139.130]) by magus.postgresql.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1jYenl-0003F8-JH for pgsql-docs@lists.postgresql.org; Tue, 12 May 2020 23:59:11 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.14.4/8.14.4) with ESMTP id 04CNx75B031431; Tue, 12 May 2020 19:59:07 -0400 From: Tom Lane To: "David G. Johnston" cc: Bruce Momjian , yigongh@gmail.com, pgsql-docs@lists.postgresql.org Subject: Re: The suggestion of reducing autovacuum_vacuum_cost_delay should be documented In-reply-to: References: <158927918783.656.11973436145559215458@wrigleys.postgresql.org> <20200512214014.GD4666@momjian.us> <20200512214101.GA21408@momjian.us> <20200512224520.GE4666@momjian.us> <23940.1589325967@sss.pgh.pa.us> <20200512233056.GF4666@momjian.us> Comments: In-reply-to "David G. Johnston" message dated "Tue, 12 May 2020 16:49:37 -0700" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <31429.1589327947.1@sss.pgh.pa.us> Date: Tue, 12 May 2020 19:59:07 -0400 Message-ID: <31430.1589327947@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Precedence: bulk "David G. Johnston" writes: > To be clear, because my cursory reading of the thread that was linked from > the commit suggested that this specific situation was more "lets catch up > to modern times", my position isn't that such documentation changes should > be done as a rule, I am suggesting that we give a yes/no decision on this > specific change (in advance of bike-shedding the wording). IMO neither a > blanket rule allowing or prohibiting such a change to the documentation > makes sense given the rarity of the event. Sure. My point was just that changing the back-branch documentation would require doing additional testing to verify that the proposed value is an improvement in those branches. regards, tom lane