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 1uyz1i-00FCwq-Ul for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Sep 2025 20:45:18 +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 1uyz1h-00B4R2-Nn for pgsql-hackers@arkaria.postgresql.org; Wed, 17 Sep 2025 20:45:17 +0000 Received: from makus.postgresql.org ([2001:4800:3e1:1::229]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1uyz1h-00B4Qu-EL for pgsql-hackers@lists.postgresql.org; Wed, 17 Sep 2025 20:45:17 +0000 Received: from momjian.us ([72.94.173.45]) by makus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.96) (envelope-from ) id 1uyz1f-000y4Z-1G for pgsql-hackers@lists.postgresql.org; Wed, 17 Sep 2025 20:45:16 +0000 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=momjian.us; s=2025010100; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description; bh=UAjdwOzB3fkPL/AK/BBvDxGMC+zulsbpf6jbGMcGchQ=; b=YOHTs aaXjQb7ifgVZiHlBwXrBWV+5elQV4iaE7Q8j6v3V/BOSw39XIbEfhhPReLvBkDjvwjv5lCr3PmBej FDUA0bqzKG2NlxWQkwu4Vp2QPqnKDrAutA/4tKKzwW1KJCJz3/nkwwSJRwreM14PnFu7l9JQCBWCs hDSIjwxYjM1+hO4aqIk9GevDlV6l72we9p1dXDcDv/IbF9MYKvWWA/DEtBLl9z2Xm8NohFoE8G6Nb svhzdS8PBaagW4mveBknwTE0zVoUk5uzeaF47BU6c/TlZ6N60C49o2SC5La9wh2CT1up2wnci//Mn yFoxpg2TRdupVuTXMgnb9y5/TImMA==; Received: from bruce by momjian.us with local (Exim 4.98.2) (envelope-from ) id 1uyz1e-00000000LUB-0Hjk; Wed, 17 Sep 2025 16:45:14 -0400 Date: Wed, 17 Sep 2025 16:45:14 -0400 From: Bruce Momjian To: Peter Geoghegan Cc: PostgreSQL-development Subject: Re: PG 18 release notes draft committed Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On Wed, Sep 17, 2025 at 11:46:58AM -0400, Peter Geoghegan wrote: > I suggest the following alternative, which has the merit of being a > bit less verbose: > > "Skip scan allows B-Tree index scans to find the most efficient way of > navigating through a multicolumn index when one or more of its columns > initially lacks a = condition and comes before a column that is > directly used by the query. Such an index scan can now be broken down > into multiple "index searches" by generating an implementation level = > condition on any underspecified columns. This allows the scan to skip > over irrelevant sections of the index, though only when the generated > = condition is on a column that has relatively few distinct values." > > Note that "index searches" is a term that now appears in EXPLAIN ANALYZE output. I went with this text, which is more "aspirational" rather than "proscriptive", and the right level of detail: This allows multi-column btree indexes to be used in more cases such as when there are no restrictions on the first or early indexed columns (or they are non-equality ones), and there are useful restrictions on later indexed columns. -- Bruce Momjian https://momjian.us EDB https://enterprisedb.com Do not let urgent matters crowd out time for investment in the future.