pg.ddx.io  pgsql-admin@postgresql.org mailing list archive  
help / color / mirror / Atom feed
effective_io_concurrency
5+ messages / 3 participants
[nested] [flat]

* effective_io_concurrency
@ 2022-01-19 17:40  Wells Oliver <wells.oliver@gmail.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Wells Oliver @ 2022-01-19 17:40 UTC (permalink / raw)
  To: pgsql-admin

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?

-- 
Wells Oliver
wells.oliver@gmail.com <wellsoliver@gmail.com>

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: effective_io_concurrency
@ 2022-01-19 17:46  Ron <ronljohnsonjr@gmail.com>
  parent: Wells Oliver <wells.oliver@gmail.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Ron @ 2022-01-19 17:46 UTC (permalink / raw)
  To: pgsql-admin@lists.postgresql.org

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.

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: effective_io_concurrency
@ 2022-01-19 18:23  Wells Oliver <wells.oliver@gmail.com>
  parent: Ron <ronljohnsonjr@gmail.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Wells Oliver @ 2022-01-19 18:23 UTC (permalink / raw)
  To: Ron <ronljohnsonjr@gmail.com>; +Cc: pgsql-admin@lists.postgresql.org

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 <wellsoliver@gmail.com>
>
>
> --
> Angular momentum makes the world go 'round.
>


-- 
Wells Oliver
wells.oliver@gmail.com <wellsoliver@gmail.com>

^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: effective_io_concurrency
@ 2022-01-19 23:19  Ian Lawrence Barwick <barwick@gmail.com>
  parent: Wells Oliver <wells.oliver@gmail.com>
  0 siblings, 1 reply; 5+ messages in thread

From: Ian Lawrence Barwick @ 2022-01-19 23:19 UTC (permalink / raw)
  To: Wells Oliver <wells.oliver@gmail.com>; +Cc: Ron <ronljohnsonjr@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>

2022年1月20日(木) 3:24 Wells Oliver <wells.oliver@gmail.com>:
>
> Understood: wanted to double check that an outright empty value would be understood by the server as 0, or otherwise.

In standard PostgreSQL, if the configuration for an integer parameter
is empty or an
empty string, an error will be raised:

postgres=# ALTER SYSTEM SET effective_io_concurrency = '';
ERROR:  invalid value for parameter "effective_io_concurrency": ""

RDS is not standard PostgreSQL though, so something else might be
going on there.

Does:

  SELECT * FROM pg_settings WHERE name = 'effective_io_concurrency'

show anything?


Regards

Ian Barwick

> 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



-- 
EnterpriseDB: https://www.enterprisedb.com





^ permalink  raw  reply  [nested|flat] 5+ messages in thread

* Re: effective_io_concurrency
@ 2022-01-19 23:34  Wells Oliver <wells.oliver@gmail.com>
  parent: Ian Lawrence Barwick <barwick@gmail.com>
  0 siblings, 0 replies; 5+ messages in thread

From: Wells Oliver @ 2022-01-19 23:34 UTC (permalink / raw)
  To: Ian Lawrence Barwick <barwick@gmail.com>; +Cc: Ron <ronljohnsonjr@gmail.com>; Pgsql-admin <pgsql-admin@lists.postgresql.org>

Looks like it's indeed 1 with an empty string in the RDS parameter groups.
Thanks all.

On Wed, Jan 19, 2022 at 3:19 PM Ian Lawrence Barwick <barwick@gmail.com>
wrote:

> 2022年1月20日(木) 3:24 Wells Oliver <wells.oliver@gmail.com>:
> >
> > Understood: wanted to double check that an outright empty value would be
> understood by the server as 0, or otherwise.
>
> In standard PostgreSQL, if the configuration for an integer parameter
> is empty or an
> empty string, an error will be raised:
>
> postgres=# ALTER SYSTEM SET effective_io_concurrency = '';
> ERROR:  invalid value for parameter "effective_io_concurrency": ""
>
> RDS is not standard PostgreSQL though, so something else might be
> going on there.
>
> Does:
>
>   SELECT * FROM pg_settings WHERE name = 'effective_io_concurrency'
>
> show anything?
>
>
> Regards
>
> Ian Barwick
>
> > 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
>
>
>
> --
> EnterpriseDB: https://www.enterprisedb.com
>


-- 
Wells Oliver
wells.oliver@gmail.com <wellsoliver@gmail.com>

^ permalink  raw  reply  [nested|flat] 5+ messages in thread


end of thread, other threads:[~2022-01-19 23:34 UTC | newest]

Thread overview: 5+ messages (download: mbox mbox.gz follow: Atom feed)
-- links below jump to the message on this page --
2022-01-19 17:40 effective_io_concurrency Wells Oliver <wells.oliver@gmail.com>
2022-01-19 17:46 ` Ron <ronljohnsonjr@gmail.com>
2022-01-19 18:23   ` Wells Oliver <wells.oliver@gmail.com>
2022-01-19 23:19     ` Ian Lawrence Barwick <barwick@gmail.com>
2022-01-19 23:34       ` Wells Oliver <wells.oliver@gmail.com>

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