Re: Passing initially_valid values instead of !skip_validation to StoreRelCheck() in AddRelationNewConstraints()

From: Marko Tiikkaja <marko(at)joh(dot)to>
To: amul sul <sul_amul(at)yahoo(dot)co(dot)in>, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org>
Subject: Re: Passing initially_valid values instead of !skip_validation to StoreRelCheck() in AddRelationNewConstraints()
Date: 2015-12-03 11:56:59
Message-ID: 56602E0B.9030402@joh.to
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers

On 12/3/15 12:44 PM, amul sul wrote:
>> On Thursday, 3 December 2015 4:36 PM, Amit Langote <Langote_Amit_f8(at)lab(dot)ntt(dot)co(dot)jp> wrote:
>> The user will have to separately validate the constraint by issuing a ALTER TABLE VALIDATE CONSTRAINT
>> command at a time of their choosing.
>
> This could be time consuming operation for big table, If I am pretty much sure that my constraint will be valid, simply I could set both flag(initially_valid & skip_validation) to true.

I'm confused here. It sounds like you're suggesting an SQL level
feature, but you're really focused on a single line of code for some
reason. Could you take a step back and explain the high level picture
of what you're trying to achieve?

.m

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Greg Stark 2015-12-03 12:10:27 Re: [RFC] overflow checks optimized away
Previous Message amul sul 2015-12-03 11:44:49 Re: Passing initially_valid values instead of !skip_validation to StoreRelCheck() in AddRelationNewConstraints()