RE: partition pruning only works for select but update - Mailing list pgsql-performance

From James Pang (chaolpan)
Subject RE: partition pruning only works for select but update
Date
Msg-id PH0PR11MB519143DAE98DDDAC0E1AB717D6B89@PH0PR11MB5191.namprd11.prod.outlook.com
Whole thread Raw
In response to Re: partition pruning only works for select but update  (Tom Lane <tgl@sss.pgh.pa.us>)
Responses RE: partition pruning only works for select but update  ("James Pang (chaolpan)" <chaolpan@cisco.com>)
List pgsql-performance
For release v14, optimizer can handle large partition counts query ( select ,update ,delete) and partition pruning is
similaras SELECT, right?  We will check option to upgrade to v14. 

Thanks,

James

-----Original Message-----
From: Tom Lane <tgl@sss.pgh.pa.us>
Sent: Tuesday, June 28, 2022 9:30 PM
To: James Pang (chaolpan) <chaolpan@cisco.com>
Cc: pgsql-performance@lists.postgresql.org
Subject: Re: partition pruning only works for select but update

"James Pang (chaolpan)" <chaolpan@cisco.com> writes:
> But when
> Explain update table set .. where  partitionkey between  to_timestamp() and to_timestamp();
>   It still show all of partitions with update ...

In releases before v14, partition pruning is far stupider for UPDATE (and DELETE) than it is for SELECT.

            regards, tom lane



pgsql-performance by date:

Previous
From: Tom Lane
Date:
Subject: Re: partition pruning only works for select but update
Next
From: Mikkel Lauritsen
Date:
Subject: Fluctuating performance of updates on small table with trigger