| From: | Mathias Kunter <mathiaskunter(at)gmail(dot)com> |
|---|---|
| To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
| Cc: | pgsql-docs(at)lists(dot)postgresql(dot)org |
| Subject: | Re: random_page_cost configuration parameter |
| Date: | 2022-01-05 18:27:55 |
| Message-ID: | 6bb6023b-fce3-801d-e799-8111cc317e35@gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-docs |
Am 28.12.21 um 17:03 schrieb Tom Lane:
> Mathias Kunter <mathiaskunter(at)gmail(dot)com> writes:
>> 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.
The default value of effective_cache_size is 4 GB. Which value should
be used instead on a system which only has 4 GB of total RAM, but still
uses RAM-cached indices?
Thank you very much for the clarification!
Best regards
Mathias Kunter
| From | Date | Subject | |
|---|---|---|---|
| Next Message | PG Doc comments form | 2022-01-06 17:38:41 | .pg_service.conf default location and default name on MS Windows platform |
| Previous Message | Bruce Momjian | 2022-01-04 22:28:04 | Re: Typo in "27.2.8. Synchronous Replication" |