RE: partition pruning only works for select but update
От | James Pang (chaolpan) |
---|---|
Тема | RE: partition pruning only works for select but update |
Дата | |
Msg-id | PH0PR11MB519143DAE98DDDAC0E1AB717D6B89@PH0PR11MB5191.namprd11.prod.outlook.com обсуждение исходный текст |
Ответ на | Re: partition pruning only works for select but update (Tom Lane <tgl@sss.pgh.pa.us>) |
Ответы |
RE: partition pruning only works for select but update
|
Список | 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 по дате отправления: