RE: partition pruning only works for select but update
От | James Pang (chaolpan) |
---|---|
Тема | RE: partition pruning only works for select but update |
Дата | |
Msg-id | PH0PR11MB5191A8D08D5B27D084BC6BFBD6BD9@PH0PR11MB5191.namprd11.prod.outlook.com обсуждение исходный текст |
Ответ на | RE: partition pruning only works for select but update ("James Pang (chaolpan)" <chaolpan@cisco.com>) |
Ответы |
Re: partition pruning only works for select but update
|
Список | pgsql-performance |
We have other application depend on V13, possible to backport code changes to V13 as https://git.postgresql.org/gitweb/?p=postgresql.git;a=patch;h=86dc90056dfdbd9d1b891718d2e5614e3e432f35 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 по дате отправления: