You signed in with another tab or window.Reload to refresh your session.You signed out in another tab or window.Reload to refresh your session.You switched accounts on another tab or window.Reload to refresh your session.Dismiss alert
Be more careful about marking catalog columns NOT NULL by default.
The bug fixed in commit72eab84 would not have occurred if initdbhad a less surprising rule about which columns should be markedNOT NULL by default. Let's make that rule be strictly that thecolumn must be fixed-width and its predecessors must be fixed-widthand NOT NULL, removing the hacky and unsafe exceptions for oidvectorand int2vector.Since we do still want all existing oidvector and int2vector columnsto be marked NOT NULL, we have to put BKI_FORCE_NOT_NULL labels onthem. But making this less magic and more documented seems like agood idea, even if it's a shade more verbose.I didn't bump catversion since the initial catalog contents arenot actually changed by this patch. Note however that thecontents of postgres.bki do change, and feeding an old copy ofthat to a new backend will produce wrong results.Discussion:https://postgr.es/m/204760.1595181800@sss.pgh.pa.us