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.
