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 1rkNWy-00CJoe-H9 for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Mar 2024 12:16:25 +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 1rkNWw-002Ab9-Qm for pgsql-hackers@arkaria.postgresql.org; Wed, 13 Mar 2024 12:16:23 +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 1rkNWw-002Ab1-D4 for pgsql-hackers@lists.postgresql.org; Wed, 13 Mar 2024 12:16:23 +0000 Received: from mail.postgrespro.ru ([93.174.131.139]) by magus.postgresql.org with esmtps (TLS1.2) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1rkNWu-004IDC-9Q for pgsql-hackers@postgresql.org; Wed, 13 Mar 2024 12:16:22 +0000 Received: from [192.168.1.41] (cm-171-100-79-98.revip10.asianet.co.th [171.100.79.98]) (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 3786CE20E67; Wed, 13 Mar 2024 15:16:12 +0300 (MSK) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=postgrespro.ru; s=mx2023; t=1710332178; bh=IOn9YSWn7AZwYAjwCphb3b5BOKkjafgoRy3R33ubM8E=; h=Message-ID:Date:User-Agent:Subject:To:Cc:References:From: In-Reply-To:From; b=D3w/bbGNpBmHX7ImK1sujw6qKmm4Lgb/NKW7USeOudjM7LSS4UCZJpgihn+6I8HnV fV/zx2MZvvwqirr5MwOzsSMyW3ZURQ1iqHPdkuAdSPojLjTb6Arg7wgtAFS6hDNW2/ TxSxTRTusasTsADC7STv9XFqGFeMd1Mp4aWacyZHm/HzdW3KXGYy3xZXQp5weXntbI bCTVqohl3Hg2tkBaHV4AlvpwThLU4tmiE5dRqDGu31AdgQcOVdWxY8vrXm5H0OT005 BkgUSdFkQuAiSTgTBcttoFitHXKc/gIXcsuAxXGEEyCTsmlg5kmeFDw48nvs9wmARb 2CxOJrG3K2lyw== Message-ID: Date: Wed, 13 Mar 2024 19:16:09 +0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: POC, WIP: OR-clause support for indexes To: Alexander Korotkov Cc: jian he , Alena Rybakina , 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> <11ee9c04-281f-43c8-a0ff-d481c1e01c09@postgrespro.ru> <54009ba5-4aea-4344-a30d-e3558a59e2a9@postgrespro.ru> <380e5683-cdfd-4220-ab9b-7cccb9d3e480@postgrespro.ru> <7389d0dd-05d5-41b7-a12d-2e73f939f851@postgrespro.ru> <74e3c8bc-dccd-45e5-ad2d-6a6e96fc5864@postgrespro.ru> Content-Language: en-US From: Andrei Lepikhov Organization: Postgres Professional In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 13/3/2024 18:05, Alexander Korotkov wrote: > On Wed, Mar 13, 2024 at 7:52 AM Andrei Lepikhov > Given all of the above, I think moving transformation to the > canonicalize_qual() would be the right way to go. Ok, I will try to move the code. I have no idea about the timings so far. I recall the last time I got bogged down in tons of duplicated code. I hope with an almost-ready sketch, it will be easier. -- regards, Andrei Lepikhov Postgres Professional