CREATE ASSERTION, or CHECK constraints with subselects
With tables that are not updated frequently, and when I'm fully aware of the performance implications, I'd like to have as many data integrity constraints as possible. I'm fully aware it can be burdensome to implement, but I cannot think of anything else to improve my current Postgres experience. Thanks for this feedback tool :)
Darren Duncan commented
CREATE ASSERTION should be supported by Postgres, because it is the most natural way to express generalized CHECK constraints that aren't specific to a single table variable, and may also be the only way to express some constraints period.