drop table t3; CREATE TABLE t3( b bigint, c int GENERATED ALWAYS AS (b * 2) VIRTUAL); insert into t3 (b) values (22147483647); ANALYZE t3;
for ANALYZE since column c has no actual storage, so it's not analyzable? we need to change the function examine_attribute accordingly? For the above example, for each insert row, we actually need to call int84 to validate c value. we probably need something similar to have ExecComputeStoredGenerated etc, but we don't need to store it.
