Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0XRr-00BxZW-VL for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Oct 2024 02:38:11 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t0XRp-0028qF-C0 for pgsql-hackers@arkaria.postgresql.org; Tue, 15 Oct 2024 02:38:09 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0XRp-0028q6-2M for pgsql-hackers@lists.postgresql.org; Tue, 15 Oct 2024 02:38:09 +0000 Received: from sss.pgh.pa.us ([68.162.161.243]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t0XRm-0016ly-Ri for pgsql-hackers@postgresql.org; Tue, 15 Oct 2024 02:38:08 +0000 Received: from sss1.sss.pgh.pa.us (localhost [127.0.0.1]) by sss.pgh.pa.us (8.15.2/8.15.2) with ESMTP id 49F2c1Iu3863755; Mon, 14 Oct 2024 22:38:01 -0400 From: Tom Lane To: David Rowley cc: Greg Sabino Mullane , =?UTF-8?Q?Dagfinn_Ilmari_Manns=C3=A5ker?= , pgsql-hackers , Bruce Momjian Subject: Re: Changing the default random_page_cost value In-reply-to: References: <877caxaxt6.fsf@wibble.ilmari.org> Comments: In-reply-to David Rowley message dated "Tue, 15 Oct 2024 15:20:31 +1300" MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <3863753.1728959881.1@sss.pgh.pa.us> Date: Mon, 14 Oct 2024 22:38:01 -0400 Message-ID: <3863754.1728959881@sss.pgh.pa.us> List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk David Rowley writes: > Yeah, I think any effort to change the default value for this setting > would require some analysis to prove that the newly proposed default > is a more suitable setting than the current default. I mean, why 1.2 > and not 1.1 or 1.3? Where's the evidence that 1.2 is the best value > for this? Yeah, that's been my main concern about this proposal too. I recall that when we settled on 4.0 as a good number for spinning-rust drives, it came out of some experimentation that I'd done that involved multiple-day-long tests. I don't recall any more details than that sadly, but perhaps trawling the mailing list archives would yield useful info. It looks like the 4.0 value came in with b1577a7c7 of 2000-02-15, so late 1999/early 2000 would be the time frame to look in. regards, tom lane