I did a moderate search in other conversations, and I couldn't find any requests for this yet.
I'm working on porting over strong migrations from ruby, and it has a check to ensure that `NOT VALID` is being set for a new reference on an existing table, because validating foreign keys on creation is a rather expensive lock
see the pg docs for Add table_constraint. When trying to implement this check for Ecto migrations, I found that there doesn't seem to be a way to pass validate: false or similar, like active_record does
here.
I could recommend users to execute raw sql to do this on their own for foreign keys, but I think Ecto offering it would be much better long term.
I also think that having a way to validate the foreign key in a subsequent migration would be a good win, but that is easy to make raw sql for.