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
Move checking for unscannable matviews into ExecOpenScanRelation, which isa better place for it first because the open relation is already available(saving a relcache lookup cycle), and second because this eliminates theproblem of telling the difference between rangetable entries that will orwill not be scanned by the query. In particular we can get rid of thenot-terribly-well-thought-out-or-implemented isResultRel field that theinitial matviews patch added to RangeTblEntry.Also get rid of entirely unnecessary scannability check in the rewriter,and a bogus decision about whether RefreshMatViewStmt requires a parse-timesnapshot.catversion bump due to removal of a RangeTblEntry field, which changesstored rules.