Re: using index or check in ALTER TABLE SET NOT NULL

Hello Sergei,

On 10.03.2018 12:35, Sergei Kornilov wrote:
> Hello My patch does not apply after commit
> 5748f3a0aa7cf78ac6979010273bd9d50869bb8e. Here is update to current
> master. Not null constraint is immutable too, so here is no changes
> in PartConstraintImpliedByRelConstraint excepts rename and comments
> fix.
>
> In this patch version i also revert tests to v4 state: i use DEBUG
> ereport instead INFO and code path not tested. Please tell me if i
> must change tests some way.
>
> regards, Sergei
>

Ok, I can't think of any other ways to test it so I have to agree with
Tom Lane i.e. rely only on coverage. (There also were another suggestion
to use statistics [select seq_scan from pg_stat_user_tables where
relid='test'::regclass] which show number of table scans. But statistics
is collected by stat collector process with some latency and hence
cannot be reliable for tests).

Patch seems correct to me, it applies and compiles cleanly, docs
compiles as well, tests pass. Changed status to Ready for Committer.

-- 
Ildar Musin
i.musin@postgrespro.ru