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

From Greg Sabino Mullane
Subject Re: Changing the default random_page_cost value
Date
Msg-id CAKAnmm+0UEcPZ0oC+7att-EAU7jXtkPJ1QcJ4v=sWzdkU92r+Q@mail.gmail.com
Whole thread Raw
In response to Re: Changing the default random_page_cost value  (Bruce Momjian <bruce@momjian.us>)
Responses Re: Changing the default random_page_cost value
List pgsql-hackers
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. :)

I would put the magnetic in a separate paragraph perhaps, and recommend
4.0 for it.

Sounds doable. Even in the pre-SSD age I recall lowering this as a fairly standard practice, but I'm fine with a recommendation of 4. Partly because I doubt anyone will use it much.

 Also, per-tablespace makes sense because of physical media
differences, but what purpose would per-database and per-role serve?
Also, per-tablespace is not a connection-activated item like the other
two.

Good point, I withdraw that part.

Cheers,
Greg

pgsql-hackers by date:

Previous
From: Andy Fan
Date:
Subject: Re: [PoC] Partition path cache
Next
From: Greg Sabino Mullane
Date:
Subject: Re: Changing the default random_page_cost value