Sorry again.
The link to letter - -
https://www.postgresql.org/message-id/759292d5-cb51-4b12-89fa-576c1d9b374d%40postgrespro.ru
Patch -
https://www.postgresql.org/message-id/attachment/162897/v28-Transform-OR-clauses-to-ANY-expression.patch
On 24.08.2024 16:23, Alexander Korotkov wrote:
On Sat, Aug 24, 2024 at 4:08 PM Alena Rybakina
<a.rybak...@postgrespro.ru> wrote:
On 23.08.2024 19:38, Alexander Korotkov wrote:
Hi, Alena!
On Fri, Aug 23, 2024 at 5:06 PM Alena Rybakina
<a.rybak...@postgrespro.ru> wrote:
To be fair, I fixed this before [0] by selecting the appropriate group
of "or" expressions to transform them to "ANY" expression and then
checking for compatibility with the index column. maybe we should try
this too? I can think about it.
[0]
https://www.postgresql.org/message-id/531fc0ab-371e-4235-97e3-dd2d077b6995%40postgrespro.ru
I probably didn't get your message. Which patch version you think
resolve the problem? I see [0] doesn't contain any patch.
Sorry, I got the links mixed up. We need this link [0].
Still confusion.
If that's another [0] from [0] in the cited message then it seems you
missed new link in your last message.
------
Regards,
Alexander Korotkov
Supabase
--
Regards,
Alena Rybakina
Postgres Professional: http://www.postgrespro.com
The Russian Postgres Company
