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
Change the planner-to-executor API so that the planner tells the executor
which comparison operators to use for plan nodes involving tuple comparison(Agg, Group, Unique, SetOp). Formerly the executor looked up the defaultequality operator for the datatype, which was really pretty shaky, since it'spossible that the data being fed to the node is sorted according to somenondefault operator class that could have an incompatible idea of equality.The planner knows what it has sorted by and therefore can provide the rightequality operator to use. Also, this change moves a couple of catalog lookupsout of the executor and into the planner, which should help startup time forpre-planned queries by some small amount. Modify the planner to remove someother cavalier assumptions about always being able to use the defaultoperators. Also add "nulls first/last" info to the Plan node for a mergejoin--- neither the executor nor the planner can cope yet, but at least the API isin place.