Re: NOT ENFORCED constraint feature - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: NOT ENFORCED constraint feature
Date
Msg-id acef3c5e-0731-45af-a709-25cfd8fbc0e8@eisentraut.org
Whole thread Raw
In response to Re: NOT ENFORCED constraint feature  (Ashutosh Bapat <ashutosh.bapat.oss@gmail.com>)
List pgsql-hackers
On 03.02.25 06:19, Ashutosh Bapat wrote:
> Here's how I see the state conversions happening.
> 
> NOT VALID, NOT ENFORCED changed to NOT_VALID, ENFORCED - no data
> validation required, constraint is enforced on the new tuples/changes
> NOT VALID, ENFORCED changed to NOT VALID, NOT ENFORCED - no data
> validation, constraint isn't enforced anymore
> VALID, NOT ENFORCED changed to VALID, ENFORCED - data validation
> required, constraint is enforced
> VALID, ENFORCED changed to VALID, NOT ENFORCED - no data validation
> required, constrain isn't enforced anymore, we rely on user to enforce
> the constraint on their side

This looks sensible to me.



pgsql-hackers by date:

Previous
From: Alena Rybakina
Date:
Subject: Re: POC: track vacuum/analyze cumulative time per relation
Next
From: Peter Eisentraut
Date:
Subject: Re: NOT ENFORCED constraint feature