For release v14, optimizer can handle large partition counts query ( select ,update ,delete) and partition pruning is similar as SELECT, right? We will check option to upgrade to v14. Thanks, James -----Original Message----- From: Tom Lane <tgl@xxxxxxxxxxxxx> Sent: Tuesday, June 28, 2022 9:30 PM To: James Pang (chaolpan) <chaolpan@xxxxxxxxx> Cc: pgsql-performance@xxxxxxxxxxxxxxxxxxxx Subject: Re: partition pruning only works for select but update "James Pang (chaolpan)" <chaolpan@xxxxxxxxx> 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
