Re: random_page_cost configuration parameter

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Mathias Kunter <mathiaskunter(at)gmail(dot)com>
Cc: pgsql-docs(at)lists(dot)postgresql(dot)org
Subject: Re: random_page_cost configuration parameter
Date: 2021-12-28 16:03:25
Message-ID: 1760891.1640707405@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-docs

Mathias Kunter <mathiaskunter(at)gmail(dot)com> writes:
> the documentation of the random_page_cost configuration parameter says:

>> Although the system will let you set random_page_cost to less than
>> seq_page_cost, it is not physically sensible to do so.

> However, I don't think this statement is true. Consider the situation
> where the randomly fetched pages are mostly (or even entirely) cached in
> RAM, but where the sequentially fetched pages must be mostly read from
> disk. An example for such a scenario is a database system which uses
> RAM-cached indices.

I think fooling with effective_cache_size is a better way to model
that situation.

regards, tom lane

In response to

Responses

Browse pgsql-docs by date

  From Date Subject
Next Message Magnus Hagander 2022-01-02 16:08:27 Re: Typo in "27.2.8. Synchronous Replication"
Previous Message Mathias Kunter 2021-12-28 10:55:00 random_page_cost configuration parameter