Re: Changing the default random_page_cost value - Mailing list pgsql-hackers

From Bruce Momjian
Subject Re: Changing the default random_page_cost value
Date
Msg-id ZyPB3KUjsL88h0h4@momjian.us
Whole thread Raw
In response to Re: Changing the default random_page_cost value  (Greg Sabino Mullane <htamfids@gmail.com>)
Responses Re: Changing the default random_page_cost value
List pgsql-hackers
On Thu, Oct 24, 2024 at 08:01:11PM -0400, Greg Sabino Mullane wrote:
> On Mon, Oct 14, 2024 at 5:15 PM Bruce Momjian <bruce@momjian.us> wrote:
> 
>     I am not a fan of this patch.  I don't see why _removing_ the magnetic
>     part helps because you then have no logic for any 1.2 was chosen.
> 
> 
> Okay, but we have no documented logic on why 4.0 was chosen either. :)

Uh, we do, and it is in the docs:

        Random access to mechanical disk storage is normally much more expensive
        than four times sequential access.  However, a lower default is used
        (4.0) because the majority of random accesses to disk, such as indexed
        reads, are assumed to be in cache.  The default value can be thought of
        as modeling random access as 40 times slower than sequential, while
        expecting 90% of random reads to be cached.

You surely saw this when you created the patch and removed the text.

-- 
  Bruce Momjian  <bruce@momjian.us>        https://momjian.us
  EDB                                      https://enterprisedb.com

  When a patient asks the doctor, "Am I going to die?", he means 
  "Am I going to die soon?"



pgsql-hackers by date:

Previous
From: "David G. Johnston"
Date:
Subject: Re: "command cannot affect row a second time" in INSERT ... ON CONFLICT
Next
From: Tom Lane
Date:
Subject: Re: Changing the default random_page_cost value