From: Ron <ronljohnsonjr@gmail.com>
To: pgsql-admin@lists.postgresql.org
Subject: Re: effective_io_concurrency
Date: Wed, 19 Jan 2022 11:46:15 -0600
Message-ID: <3a5e6f9f-9dd7-1f3f-2086-36a331259ff5@gmail.com> (raw)
In-Reply-To: <CAOC+FBXXqWzV-5fjG8zxRcgg6c_ihq6n9-3WYrUo_gdmJx8sCQ@mail.gmail.com>
References: <CAOC+FBXXqWzV-5fjG8zxRcgg6c_ihq6n9-3WYrUo_gdmJx8sCQ@mail.gmail.com>
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 <mailto:wellsoliver@gmail.com>
--
Angular momentum makes the world go 'round.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: ronljohnsonjr@gmail.com, pgsql-admin@lists.postgresql.org
Subject: Re: effective_io_concurrency
In-Reply-To: <3a5e6f9f-9dd7-1f3f-2086-36a331259ff5@gmail.com>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox