Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t34ol-00A8tD-9e for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Oct 2024 02:40:19 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1t34oj-00DOyf-3i for pgsql-hackers@arkaria.postgresql.org; Tue, 22 Oct 2024 02:40:17 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1t34oi-00DOyW-QO for pgsql-hackers@lists.postgresql.org; Tue, 22 Oct 2024 02:40:17 +0000 Received: from mail-oa1-x34.google.com ([2001:4860:4864:20::34]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256 (Exim 4.94.2) (envelope-from ) id 1t34og-002Jns-Ub for pgsql-hackers@postgresql.org; Tue, 22 Oct 2024 02:40:16 +0000 Received: by mail-oa1-x34.google.com with SMTP id 586e51a60fabf-2884e7fadb8so2602459fac.2 for ; Mon, 21 Oct 2024 19:40:14 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1729564811; x=1730169611; darn=postgresql.org; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=FixwL2GNgGUrGRupJ7V7wBJcMrhAMVEtHL3ctB5Ff/o=; b=Mz52vK/wyfhB9r7etCs9ctx/t/WEDDHlrHLJ8KOCMJ8t0hACT+tEmus3PNulW7ymNf JPkQyipLCzDsfjOxknYGQLf71EhB3tqJo7+PvkbyJLZMCEpIO2xghyiNk4AxPaVj39v8 C18LEaEbUMrMIpKu1NnSSzJIDLPAPvWzISfPmcBG5r+KqLPtGikffmLSOEsBM2lH2j0K X05jX+n1dfBIyCsLGwicDuz0/B0P67JzQcdscwbWW7zeIXWm7MsKB7BOVsfSorCqEfSU 41gcYLAWKYoOg+s+2LZSBHRODHE3gPS3DL5x5OHbo3JCVCSArL2DAkKox867tlNQG5sx xwfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1729564811; x=1730169611; h=cc:to:subject:message-id:date:from:references:in-reply-to :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=FixwL2GNgGUrGRupJ7V7wBJcMrhAMVEtHL3ctB5Ff/o=; b=sgG4ru1bJyjrvmDTwkgyUHolCCb6EW1fbrFS1vKd/vdjlbLXWMlS/4K6P8OUp2Tx5K DrIDpWIvarUC1h4ui3t3yyIy7ABLA6KCuYXKGeex+DkseX2oNlxk39qjQr8cmlBuTkOK +lnaTqPZpypkklQFTZaGxx22oJLjZHmsA+VKyNrrMUMk8RyufQGne9f3iZ8tu3H8adS2 jokHANO+I4FlEmEckbhjquD98KBAO9aOx3Q5OauHSnQNbA4cLMQz97xQ0Vd5lhheTO/y /K8BL190sFCSTl68weIRlSnQePGTUibT66+5XDqw91nLQwA/U1U8gar+bq0KxIMC22Ci WwAA== X-Forwarded-Encrypted: i=1; AJvYcCVN08klcEkaBo7/YCX8F0KEQVTZ/dq3ZzugQi/jGmHFVZGX88PUePEadYtH0PowzEphaIwANeywki9kB69G@postgresql.org X-Gm-Message-State: AOJu0YxJtoJKtIXdk9SSXGVLDBLkBvY3YEINtGJ/UI4qkhypVWOTfGco tkzt1dvr2NnBaKmFQrL+Q1lbh8g7GAztBa34hDWutzFi50vLZtt1u7dzNBghUBrWDWCso05zor1 vq/7Mva2TSlhuHD5AH2+crhWHIA4= X-Google-Smtp-Source: AGHT+IGOXKD/mcDWnEQ6o0NUPlCpM1FMhJ3UY+/jFHntEGm2n68NowVJL3mNB6kQy9UqlCps6aSNQzhDI9kKrUr7+LM= X-Received: by 2002:a05:6870:2183:b0:288:2b44:5577 with SMTP id 586e51a60fabf-2892c2e91f8mr10464361fac.18.1729564811637; Mon, 21 Oct 2024 19:40:11 -0700 (PDT) MIME-Version: 1.0 Received: by 2002:a8a:e87:0:b0:56c:c9af:3ee6 with HTTP; Mon, 21 Oct 2024 19:40:11 -0700 (PDT) In-Reply-To: References: From: "David G. Johnston" Date: Mon, 21 Oct 2024 19:40:11 -0700 Message-ID: Subject: Re: EXPLAIN IndexOnlyScan shows disabled when enable_indexonlyscan=on To: David Rowley Cc: Melanie Plageman , Pg Hackers , Robert Haas Content-Type: multipart/alternative; boundary="00000000000036c0d7062507b0a3" List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk --00000000000036c0d7062507b0a3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, October 21, 2024, David Rowley wrote: > On Tue, 22 Oct 2024 at 14:46, David G. Johnston > wrote: > > We should probably at least improve the documentation in 19.17.1; this > interaction is apparently not self-evident. > > > > enable_indexscan > > > > Enable or disable the planner=E2=80=99s use of both index-scan and > index-only-scans plan types. > > > > enabled_indexonlyscan > > > > Set to off to disable index-only-scan plan type while leaving index-sca= n > plan types enabled. This setting has no effect if enable_indexscan is se= t > to off. > > Yeah, I agree. The documentation could better reflect the current > behaviour. > > Do you want to submit that in patch form? > Will do tomorrow. David J. --00000000000036c0d7062507b0a3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable On Monday, October 21, 2024, David Rowley <dgrowleyml@gmail.com> wrote:
On Tue, 22 Oct 2024 at 14:46, David G. Johnston
<david.g.johnston@gmail.co= m> wrote:
> We should probably at least improve the documentation in 19.17.1; this= interaction is apparently not self-evident.
>
> enable_indexscan
>
> Enable or disable the planner=E2=80=99s use of both index-scan and ind= ex-only-scans plan types.
>
> enabled_indexonlyscan
>
> Set to off to disable index-only-scan plan type while leaving index-sc= an plan types enabled.=C2=A0 This setting has no effect if enable_indexscan= is set to off.

Yeah, I agree. The documentation could better reflect the current behaviour= .

Do you want to submit that in patch form?

Will do tomorrow.

David J.
=C2=A0
--00000000000036c0d7062507b0a3--