Re: Suggestion: provide a "TRUNCATE PARTITION" command
| От | Thomas Kellerer |
|---|---|
| Тема | Re: Suggestion: provide a "TRUNCATE PARTITION" command |
| Дата | |
| Msg-id | 5f752f45-67ff-456b-5904-14b1782576bd@gmx.net обсуждение исходный текст |
| Ответ на | Re: Suggestion: provide a "TRUNCATE PARTITION" command (Michael Lewis <mlewis@entrata.com>) |
| Ответы |
Re: Suggestion: provide a "TRUNCATE PARTITION" command
Re: Suggestion: provide a "TRUNCATE PARTITION" command |
| Список | pgsql-general |
Michael Lewis schrieb am 08.01.2021 um 17:47: > > For me, it seems too easily error prone such that a single typo in > > the IN clause may result in an entire partition being removed that > > wasn't supposed to be targeted. > > I don't see how this is more dangerous then: > > delete from base_table > where partition_key in (...); > > which would serve the same purpose, albeit less efficient. > > > Delete has a rollback option, and you can dry-run to see impacted rows effectively. Truncate does not. TRUNCATE can be rolled back as well.
В списке pgsql-general по дате отправления: