Re: Mutability of domain CHECK constraints

Vik Fearing <vik.fearing@2ndquadrant.com>

From: Vik Fearing <vik.fearing@2ndquadrant.com>
To: Tom Lane <tgl@sss.pgh.pa.us>, pgsql-hackers@lists.postgresql.org
Date: 2018-12-29T23:03:04Z
Lists: pgsql-hackers
On 06/12/2018 15:41, Tom Lane wrote:
> So what I'm thinking we should do is document that the behavior of a
> domain CHECK constraint is expected to be immutable, and it's on the
> user's head to preserve consistency if it isn't.  We could recommend
> that any attempt to change a constraint's behavior be implemented by
> dropping and re-adding the constraint, which is a case that the system
> does know what to do with.
> 
> Actually, the same goes for table CHECK constraints ...

I got annoyed several years ago that CHECK constraints aren't required
to be immutable.  I don't understand why that's the case but there's a
regression test specifically for it so I never did anything about it.
-- 
Vik Fearing                                          +33 6 46 75 15 36
http://2ndQuadrant.fr     PostgreSQL : Expertise, Formation et Support


Commits

  1. Doc: document that we expect CHECK constraint conditions to be immutable.