Postgres Pro
Downloads
Home   >   mailing lists

Re: using index or check in ALTER TABLE SET NOT NULL - Mailing list pgsql-hackers

From Peter Eisentraut
Subject Re: using index or check in ALTER TABLE SET NOT NULL
Date
Msg-id b74455c1-f89e-02e3-471a-8fdd9275fab9@2ndquadrant.com
Whole thread Raw
In response to Re: using index or check in ALTER TABLE SET NOT NULL  (Sergei Kornilov <sk@zsrv.org>)
Responses Re: using index or check in ALTER TABLE SET NOT NULL  (Sergei Kornilov <sk@zsrv.org>)
List pgsql-hackers
Tree view 
On 11/29/17 10:52, Sergei Kornilov wrote:
> My target problem of adding NOT NULL to big relation without long downtime can be done with ADD CONSTRAINT NOT VALID,
VALIDATEit in second transaction, then SET NOT NULL by my patch and drop unneeded constraint.
 

It seems to me that this is a workaround for not properly cataloguing
NOT NULL constraints.  If we fixed that, you could do SET NOT NULL NOT
VALID and go from there.  Maybe we should look again into fixing that.
That would solve so many problems.

-- 
Peter Eisentraut              http://www.2ndQuadrant.com/
PostgreSQL Development, 24x7 Support, Remote DBA, Training & Services

pgsql-hackers by date:

Previous
From: David Rowley
Date:
Subject: Re: [HACKERS] Runtime Partition Pruning
Next
From: Tom Lane
Date:
Subject: Re: WIP: a way forward on bootstrap data