Re: FK violation in partitioned table after truncating a referenced partition
Alvaro Herrera <alvherre@2ndquadrant.com>
From: Alvaro Herrera <alvherre@2ndquadrant.com>
To: Jehan-Guillaume de Rorthais <jgdr@dalibo.com>
Cc: pgsql-bugs@lists.postgresql.org
Date: 2020-02-06T22:00:05Z
Lists: pgsql-bugs
Also, I think we should patch the documentation like this, because this effect is not 100% obvious. (For example, if the partition strategy is identical in both referenced and referencing tables, you would wish that only the equivalent partition is truncated. However, I doubt this can be really implemented.) I do wonder how do other RDBMSs behave. -- Álvaro Herrera https://www.2ndQuadrant.com/ PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services
Commits
-
Fix TRUNCATE .. CASCADE on partitions
- ce054a8cd4f4 12.2 landed
- 9710d3d4a87f 13.0 landed