Re: POC, WIP: OR-clause support for indexes

From: Andrei Lepikhov <lepihov(at)gmail(dot)com>
To: Alexander Korotkov <aekorotkov(at)gmail(dot)com>
Cc: Alena Rybakina <a(dot)rybakina(at)postgrespro(dot)ru>, jian he <jian(dot)universality(at)gmail(dot)com>, Nikolay Shaplov <dhyan(at)nataraj(dot)su>, pgsql-hackers(at)lists(dot)postgresql(dot)org, Robert Haas <robertmhaas(at)gmail(dot)com>, pgsql-hackers(at)postgresql(dot)org, Peter Geoghegan <pg(at)bowt(dot)ie>, Marcos Pegoraro <marcos(at)f10(dot)com(dot)br>, teodor(at)sigaev(dot)ru, Peter Eisentraut <peter(at)eisentraut(dot)org>, Ranier Vilela <ranier(dot)vf(at)gmail(dot)com>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
Subject: Re: POC, WIP: OR-clause support for indexes
Date: 2024-10-02 06:45:11
Message-ID: d190304b-17ca-452e-9c2b-e9a84f3257bc@gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 1/10/2024 12:25, Alexander Korotkov wrote:
> I think this patchset got much better, and it could possible be
> committed after another round of cleanup and comment/docs improvement.
> It would be very kind if you share your view on the decisions made in
> this patchset.
I went through the code one more time. It is awesome how the initial
idea has changed. Now, it really is a big deal—thanks for your
inspiration on where to apply this transformation.
As I see it, it helps to avoid the linear growth of execution time for
BitmapOr paths. Also, it opens up room for further improvements related
to OR-clauses alternative groupings and (maybe it is an enterprise-grade
feature) removing duplicated constants from the array.

--
regards, Andrei Lepikhov

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Michael Paquier 2024-10-02 07:15:55 Re: Return pg_control from pg_backup_stop().
Previous Message Yugo NAGATA 2024-10-02 06:39:54 Re: Enhance create subscription reference manual