Re: no partition pruning when partitioning using array type - Mailing list pgsql-hackers

From Alvaro Herrera
Subject Re: no partition pruning when partitioning using array type
Date
Msg-id 20180710194857.ifkzitgvnlf6xoxz@alvherre.pgsql
Whole thread Raw
In response to Re: no partition pruning when partitioning using array type  (Alvaro Herrera <alvherre@2ndquadrant.com>)
Responses Re: no partition pruning when partitioning using array type  (Amit Langote <Langote_Amit_f8@lab.ntt.co.jp>)
List pgsql-hackers
On 2018-Jul-10, Alvaro Herrera wrote:

> alvherre=# explain update p set a = a || a where a = '{1}';
>                         QUERY PLAN                        
> ──────────────────────────────────────────────────────────
>  Update on p  (cost=0.00..54.03 rows=14 width=38)
>    Update on p1
>    Update on p2
>    ->  Seq Scan on p1  (cost=0.00..27.02 rows=7 width=38)
>          Filter: (a = '{1}'::integer[])
>    ->  Seq Scan on p2  (cost=0.00..27.02 rows=7 width=38)
>          Filter: (a = '{1}'::integer[])
> (7 filas)
> 
> Because UPDATE uses the predtest.c prune code, not partprune.  So it's
> not just some ruleutils beautification.

I added this test, modified some comments, and pushed.

Thanks for the patch.

-- 
Álvaro Herrera                https://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services


pgsql-hackers by date:

Previous
From: Tom Lane
Date:
Subject: Re: Failure assertion in GROUPS mode of window function in current HEAD
Next
From: Alvaro Herrera
Date:
Subject: Re: no partition pruning when partitioning using array type