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
This patch fixes two inadequacies of the PlanRowMark representation.First, that the original LockingClauseStrength isn't stored (and cannot beinferred for foreign tables, which always get ROW_MARK_COPY). Since somePlanRowMarks are created out of whole cloth and don't actually have anancestral RowMarkClause, this requires adding a dummy LCS_NONE value toenum LockingClauseStrength, which is fairly annoying but the alternativesseem worse. This fix allows getting rid of the use of get_parse_rowmark()in FDWs (as per the discussion around commits462bd95 and8ec8760), and it simplifies some things elsewhere.Second, that the representation assumed that all child tables in aninheritance hierarchy would use the same RowMarkType. That's true todaybut will soon not be true. We add an "allMarkTypes" field that identifiesthe union of mark types used in all a parent table's children, and usethat where appropriate (currently, only in preprocess_targetlist()).In passing fix a couple of minor infelicities left over from the SKIPLOCKED patch, notably that _outPlanRowMark still thought waitPolicyis a bool.Catversion bump is required because the numeric values of enumLockingClauseStrength can appear in on-disk rules.Extracted from a much larger patch to support foreign table inheritance;it seemed worth breaking this out, since it's a separable concern.Shigeru Hanada and Etsuro Fujita, somewhat modified by me