Re: Should we update the random_page_cost default value?

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: Bruce Momjian <bruce(at)momjian(dot)us>
Cc: Andres Freund <andres(at)anarazel(dot)de>, Tomas Vondra <tomas(at)vondra(dot)me>, PostgreSQL Hackers <pgsql-hackers(at)lists(dot)postgresql(dot)org>
Subject: Re: Should we update the random_page_cost default value?
Date: 2025-10-09 12:05:37
Message-ID: CA+TgmobD6Edv-6zh+9L7pntSVgpq9_AGYvOdcseyNh2a_BUW0A@mail.gmail.com
Views: Whole Thread | Raw Message | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On Wed, Oct 8, 2025 at 8:16 PM Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> I rewrote the random_page_cost docs, attached, to remove a focus on
> magnetic disk, and added network latency as a reason for
> random_page_cost being low. I removed the specific caching numbers and
> went with a more generic description.
>
> I would normally apply this only to master, but given the complaints in
> this thread, maybe I should backpatch it.

This seems fine to me but I won't be surprised if other people have
some complaints. :-)

--
Robert Haas
EDB: http://www.enterprisedb.com

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Andres Freund 2025-10-09 12:08:05 memory leak in dbase_redo()
Previous Message Shinya Kato 2025-10-09 12:04:20 Re: Add mode column to pg_stat_progress_vacuum