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 1rfVYz-000blW-9o for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Feb 2024 01:50:22 +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 1rfVYx-00GeWq-8h for pgsql-hackers@arkaria.postgresql.org; Thu, 29 Feb 2024 01:50:19 +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 1rfVYw-00GeWO-RE for pgsql-hackers@lists.postgresql.org; Thu, 29 Feb 2024 01:50:19 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by makus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rfVYs-001z97-Fg for pgsql-hackers@postgresql.org; Thu, 29 Feb 2024 01:50:17 +0000 Received: from [172.30.0.166] (unknown [172.30.0.166]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client did not present a certificate) (Authenticated sender: a.lepikhov@postgrespro.ru) by mail.postgrespro.ru (Postfix/587) with ESMTPSA id 5A5FDE21140; Thu, 29 Feb 2024 04:50:09 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1709171411; bh=xp4Lnq5hyoDOYhz995hpIIPii2JZIJR8LwArdpwE35Y=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=SVdorhFuq3pl44KphDoPmnNF8MoQb9PDdqKaZ3txouq2aJYxmp4JAe2d+5xHG87SE jol2Nv87tp+A7Nz5cKdoCQFL4dUWv4QVCFYd5UNDxdM+VO0L6ajWKAAaa4vzcJD0jz BFvTR1af7BI7EiKlTsRUQvClz/c8Qu8q+eqy7aGdGi0Ssx0AKWQXqbHuiYiunB2eDC omFaGfk37j0yOEzJDXHUSYaYy9A+1+aDxqNObYF7DIlJF7gcbtHQNW1wgsDsIrlSAa jtu5rIHmEcMSEi4a16b0GqPAOqyQJMn9eWpU3dPnIF7pq7gXy5F110fSz1+Xe5/uQF AtAoG5z1WeyiA== Message-ID: <6796cc76-01a1-4541-93bb-e478fb9bcc30@postgrespro.ru> Date: Thu, 29 Feb 2024 08:50:06 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: POC, WIP: OR-clause support for indexes Content-Language: en-US To: jian he Cc: Alena Rybakina , Alexander Korotkov , Robert Haas , pgsql-hackers@postgresql.org, Peter Geoghegan , "Finnerty, Jim" , Marcos Pegoraro , teodor@sigaev.ru, Tomas Vondra , Peter Eisentraut , Ranier Vilela References: <567ED6CA.2040504@sigaev.ru> <13ad923a-33df-4b44-9e00-c9323cd4c37d@postgrespro.ru> <1cf6b382-6e27-4268-9f2a-54ada66eb2eb@postgrespro.ru> <5f119769-ab11-4807-abcc-71d5dd914ea0@postgrespro.ru> <21088129-7cd3-424a-bcce-6a3427ba3276@postgrespro.ru> <11ee9c04-281f-43c8-a0ff-d481c1e01c09@postgrespro.ru> From: Andrei Lepikhov Organization: Postgres Professional In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 28/2/2024 17:07, jian he wrote: > doc/src/sgml/array.sgml corresponds to > https://www.postgresql.org/docs/current/arrays.html. > this GUC is related to parser|optimzier. > adding a GUC to array.sgml seems strange. (I think). Maybe. In that case, I suggest adding extended comments to functions transformBoolExprOr and generate_saop_pathlist (including cross-referencing each other). These are starting points to understand the transformation and, therefore, a good place for a detailed explanation. -- regards, Andrei Lepikhov Postgres Professional