From: | Wells Oliver <wells(dot)oliver(at)gmail(dot)com> |
---|---|
To: | Ron <ronljohnsonjr(at)gmail(dot)com> |
Cc: | pgsql-admin(at)lists(dot)postgresql(dot)org |
Subject: | Re: effective_io_concurrency |
Date: | 2022-01-19 18:23:55 |
Message-ID: | CAOC+FBV7BVzz+sHUWMx8xGpVMCFZSA+UBi9E9d5QU90GAdD8+A@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-admin |
Understood: wanted to double check that an outright empty value would be
understood by the server as 0, or otherwise.
On Wed, Jan 19, 2022 at 9:46 AM Ron <ronljohnsonjr(at)gmail(dot)com> wrote:
> On 1/19/22 11:40 AM, Wells Oliver wrote:
>
> Hi all-- I notice in the default PG 13 settings for Postgres on
> RDS, effective_io_concurrency is empty, and doing a
> "show effective_io_concurrency" also shows an empty value-- what's the
> effect of this? That PG assumes 0 for the setting?
>
>
> https://www.postgresql.org/docs/13/runtime-config-resource.html
>
> "The allowed range is 1 to 1000, or *zero to disable issuance of
> asynchronous I/O requests*. Currently, this setting only affects bitmap
> heap scans."
>
> --
> Wells Oliver
> wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
>
>
> --
> Angular momentum makes the world go 'round.
>
--
Wells Oliver
wells(dot)oliver(at)gmail(dot)com <wellsoliver(at)gmail(dot)com>
From | Date | Subject | |
---|---|---|---|
Next Message | Wells Oliver | 2022-01-19 21:38:17 | Setting effective_cache_size in integer form with the 8kb block units |
Previous Message | Ron | 2022-01-19 17:46:15 | Re: effective_io_concurrency |