Re: effective_io_concurrency
| От | Wells Oliver |
|---|---|
| Тема | Re: effective_io_concurrency |
| Дата | |
| Msg-id | CAOC+FBV7BVzz+sHUWMx8xGpVMCFZSA+UBi9E9d5QU90GAdD8+A@mail.gmail.com обсуждение исходный текст |
| Ответ на | Re: effective_io_concurrency (Ron <ronljohnsonjr@gmail.com>) |
| Ответы |
Re: effective_io_concurrency
|
| Список | 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@gmail.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.oliver@gmail.com--
Angular momentum makes the world go 'round.
Wells Oliver
wells.oliver@gmail.com
wells.oliver@gmail.com
В списке pgsql-admin по дате отправления: