Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAF2P-0000nG-Fa for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jan 2022 17:46:25 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.92) (envelope-from ) id 1nAF2O-0004Rs-B4 for pgsql-admin@arkaria.postgresql.org; Wed, 19 Jan 2022 17:46:24 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_256_GCM_SHA384:256) (Exim 4.92) (envelope-from ) id 1nAF2N-0004Rj-V8 for pgsql-admin@lists.postgresql.org; Wed, 19 Jan 2022 17:46:24 +0000 Received: from mail-ot1-x32c.google.com ([2607:f8b0:4864:20::32c]) by makus.postgresql.org with esmtps (TLS1.3:ECDHE_RSA_AES_128_GCM_SHA256:128) (Exim 4.92) (envelope-from ) id 1nAF2H-0007KM-5v for pgsql-admin@lists.postgresql.org; Wed, 19 Jan 2022 17:46:22 +0000 Received: by mail-ot1-x32c.google.com with SMTP id a12-20020a0568301dcc00b005919e149b4cso4086024otj.8 for ; Wed, 19 Jan 2022 09:46:17 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=subject:to:references:from:message-id:date:user-agent:mime-version :in-reply-to:content-language; bh=FQVdFXgzlphrRVowVrRUU6ppaMqUDHmWK6DzxGDh3mk=; b=jDFkgzBhHc2SIqzVV5x0tqtBfbQ0yfBkIf7rh6RPGaJSD8VFn5wD4dE8OoxTObqzAh MmgFQa6XAFDJ2RA7rCjMufO1+Qy4YEO1gROSRE0RfvA73IOuo8Vv14ULCufasqtCgj9i aIS9AOj92EvAMX3BzklDoi4RSQpf0jyaU/6qhRu5V0c1FgwoALrJFbnJE/sZtV5UdIEL 0Bi3bdAPbL599cWwQBioxtWV7ygUza5IABps8KsAc6HAwko3MCwxFOuJJAFYeQDU/I4o c7J7B+Veuv4/EV07kBK8+nimrqAFznP7NOfTZuBhz8myD/S4X2KQTFi4teC+zOSuxrWQ XApQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language; bh=FQVdFXgzlphrRVowVrRUU6ppaMqUDHmWK6DzxGDh3mk=; b=GMNYZtZFMDeajl+kUDaU/HaWyK/CYmm/wFSQgx4Q1cSJ1hONgvIbpk0NBdWgupfZSx 7zBNICY5zLcFm6cSz9CX+/7L9Q/rUVemUP1V8COjkePUdoDYjDEbVOcHUXo2dkJglkEn gqM7A0AW4H0R+2rRdCGg0oqrYvwClv9z6rPoMqe9n3S6VWVQuUZfuS59j7m0/s1H+QO/ kEg0PD7GSz6sG4Y1XiSMk4hHhBM6rZbwsB7qqxelCQsKZwxoh09SYx281bS62IKnXCSS PIYQj8vbaOYPSZc6iWvE5OOE3Jj4e3ciskmmj0Ol1MSeP3oTSfO8P79Gz4gMvWHPjrxY BLZg== X-Gm-Message-State: AOAM5339LGx/dcsELP0la34wt+mabcHFVovB++qqG+1zOHA6niaAfCyT S0uCqeO89eWg8n2kGcZNX/L5XEiU4+w= X-Google-Smtp-Source: ABdhPJxqA9vq7wkarg6gUr6K8Iw9XxGVpeMBEWZdVcXdSXqcyqx5yWAsV9B4uYCsO7Oo0msyDZBq+g== X-Received: by 2002:a05:6830:3152:: with SMTP id c18mr14511391ots.183.1642614376360; Wed, 19 Jan 2022 09:46:16 -0800 (PST) Received: from [192.168.88.10] (ip68-11-68-85.no.no.cox.net. [68.11.68.85]) by smtp.googlemail.com with ESMTPSA id i13sm163472otl.46.2022.01.19.09.46.15 for (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 19 Jan 2022 09:46:15 -0800 (PST) Subject: Re: effective_io_concurrency To: pgsql-admin@lists.postgresql.org References: From: Ron Message-ID: <3a5e6f9f-9dd7-1f3f-2086-36a331259ff5@gmail.com> Date: Wed, 19 Jan 2022 11:46:15 -0600 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.14.0 MIME-Version: 1.0 In-Reply-To: Content-Type: multipart/alternative; boundary="------------C0A4AEE3F7697C0DA174E271" Content-Language: en-US List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk This is a multi-part message in MIME format. --------------C0A4AEE3F7697C0DA174E271 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit 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. --------------C0A4AEE3F7697C0DA174E271 Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 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."

--

--
Angular momentum makes the world go 'round.
--------------C0A4AEE3F7697C0DA174E271--