scalar subquery around it.
I'm a bit lost. It seems like postgres is fully capable of pruning
partitions for =ANY checks, and some strange detail is confusing it in this
case. I'm not sure what else to try.
On Wed, Aug 7, 2024 at 6:10 PM Marcelo Zabani wrote:
> Hello all. I am
Hello all. I am trying to make postgres 16 prune partition for queries with
`WHERE tenant_id=ANY(current_setting('my.tenant_id')::integer[])`, but I
haven't been able to make it work, and naturally it impacts performance so
I thought this list would be appropriate.
Here's the SQL I tried (but feel
