Changes between Initial Version and Version 1 of Ticket #31653, comment 4
- Timestamp:
- Jun 3, 2020, 7:44:40 AM (5 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #31653, comment 4
initial v1 5 5 My interpretation is that in order for other transactions to ''see'' that the constraint was added in a `READ COMMITTED` scenario the `ADD CONSTRAINT NOT VALID` must be committed first; performing a `ADD CONSTRAINT NOT VALID` and `VALIDATE CONSTRAINT` in the same transaction should result in the same operations as `ADD CONSTRAINT` otherwise PostgreSQL would always do it by default? 6 6 7 I could be missing something as I didn't try it out locally but from my understanding this would need the following se tof migrations to be generated to work properly.7 I could be missing something as I didn't try it out locally but from my understanding this would need the following sequence of migrations to be generated to work properly. 8 8 9 9 {{{#!python