| From: | Pavel Stehule <pavel(dot)stehule(at)gmail(dot)com> |
|---|---|
| To: | Andrei Lepikhov <lepihov(at)gmail(dot)com> |
| Cc: | pgsql-hackers <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Prune partitions by ScalarArrayOpExpr with an array parameter (partkey = ANY($1)) |
| Date: | 2025-03-17 17:01:22 |
| Message-ID: | CAFj8pRCUy6nipGfEBYrhAoOQbCJZtwCiWuvmL_u=Vh3qTxEgsg@mail.gmail.com |
| Views: | Whole Thread | Raw Message | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
po 17. 3. 2025 v 14:28 odesílatel Andrei Lepikhov <lepihov(at)gmail(dot)com>
napsal:
> Hi,
>
> As I see, initial pruning doesn't work in the case when a
> ScalarArrayOpExpr contains a parameter as the RHS of the expression,
> like following:
>
> partkey = ANY($1)
>
> As colleagues say, it is quite typical to use stored procedures, pass an
> array of IDs as a parameter, and use it in a SELECT clause.
>
> So, here I propose a patch that extends pruning machinery. It is nothing
> innovative or complicated, but I'm not sure it is fully operational so
> far: it may need some discussion, review and polishing.
>
> I intended to add it to the next commitfest if this feature makes sense.
>
+1
Pavel
> --
> regards, Andrei Lepikhov
>
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Masahiko Sawada | 2025-03-17 17:02:17 | Re: Skip collecting decoded changes of already-aborted transactions |
| Previous Message | Srirama Kucherlapati | 2025-03-17 16:58:04 | RE: AIX support |