public inbox for [email protected]  
help / color / mirror / Atom feed
From: Alena Rybakina <[email protected]>
To: Alexander Korotkov <[email protected]>
To: Andrei Lepikhov <[email protected]>
To: jian he <[email protected]>
Cc: Robert Haas <[email protected]>
Cc: [email protected]
Cc: Peter Geoghegan <[email protected]>
Cc: Finnerty, Jim <[email protected]>
Cc: Marcos Pegoraro <[email protected]>
Cc: [email protected]
Cc: Tomas Vondra <[email protected]>
Cc: Peter Eisentraut <[email protected]>
Cc: Ranier Vilela <[email protected]>
Subject: Re: POC, WIP: OR-clause support for indexes
Date: Sun, 3 Mar 2024 12:26:19 +0300
Message-ID: <[email protected]> (raw)
In-Reply-To: <CAPpHfds=4kTMhrdijV2hxL4o1ffyceZ+p95KxnF2zBTOb12LWg@mail.gmail.com>
References: <[email protected]>
	<[email protected]>
	<CACJufxH-zju3VfosSRBu8d3xs99sGENn6+P3AETLuTiAPFY+0g@mail.gmail.com>
	<[email protected]>
	<CACJufxFMFoosvbuFYDiFtpam4sKCSGJeh5jYiZSY8PHjCpEHYA@mail.gmail.com>
	<[email protected]>
	<CAEudQAq4XTcwhw2OmfW1AJNqvMfbReEWjuzqv6YTz6ZjbpmL0g@mail.gmail.com>
	<[email protected]>
	<CAEudQArk002t_C9LGoeJWnw=iGKikt+gSa8Mh==muG00WS=qYA@mail.gmail.com>
	<CACJufxFhQn0awSEcZD7=FHvjx6OLt6PUtuoi0_10pWFVXUEDJw@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CACJufxGqLA32zTtaJRL2Cacp771k6PJnau7gsax0KRV434Qq7w@mail.gmail.com>
	<[email protected]>
	<[email protected]>
	<CAPpHfds=4kTMhrdijV2hxL4o1ffyceZ+p95KxnF2zBTOb12LWg@mail.gmail.com>

I found that it was mentioned here - 
https://www.postgresql.org/message-id/CACJufxFrZS07oBHMk1_c8P3A84VZ3ysXiZV8NeU6gAnvu%2BHsVA%40mail.g....

To be honest, I couldn't find any explanation for that.

On 01.03.2024 18:33, Alexander Korotkov wrote:
> Hi, Andrei,
> Hi, Alena!
>
> On Thu, Feb 29, 2024 at 10:59 AM Andrei Lepikhov 
> <[email protected]> wrote:
>
>     On 28/2/2024 17:27, Alena Rybakina wrote:
>     > Maybe like that:
>     >
>     > It also considers the way to generate a path using BitmapScan
>     indexes,
>     > converting the transformed expression into expressions separated
>     by "OR"
>     > operations, and if it turns out to be the best and finally
>     selects the
>     > best one.
>     Thanks,
>     I spent some time describing the feature with documentation.
>     A condensed description of the GUC is in the runtime-config file.
>     Feature description has spread between TransformOrExprToANY and
>     generate_saop_pathlist routines.
>     Also, I've made tiny changes in the code to look more smoothly.
>     All modifications are integrated into the two new patches.
>
>     Feel free to add, change or totally rewrite these changes.
>
>
> I'm going to review and revise the patch.
>
> One question I have yet.
>
> >        /*
> >         * Transformation only works with both side type is not
> >         * { array | composite | domain | record }.
>
> Why do we limit transformation for these types?  Also, it doesn't seem 
> the current code restricts anything except composite/record.
>
> ------
> Regards,
> Alexander Korotkov

-- 
Regards,
Alena Rybakina
Postgres Professional:http://www.postgrespro.com
The Russian Postgres Company


view thread (41+ messages)  latest in thread

reply

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Reply to all the recipients using the --to and --cc options:
  reply via email

  To: [email protected]
  Cc: [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected], [email protected]
  Subject: Re: POC, WIP: OR-clause support for indexes
  In-Reply-To: <[email protected]>

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

This inbox is served by agora; see mirroring instructions
for how to clone and mirror all data and code used for this inbox