pgsql: Relax some asserts in merge join costing code

2020-10-19 Thread David Rowley
Relax some asserts in merge join costing code In the planner, it was possible, given an extreme enough case containing a large number of joins for the number of estimated rows to become infinite. This could cause problems in initial_cost_mergejoin() where we perform some calculations based on thos

pgsql: Relax some asserts in merge join costing code

2020-10-19 Thread David Rowley
Relax some asserts in merge join costing code In the planner, it was possible, given an extreme enough case containing a large number of joins for the number of estimated rows to become infinite. This could cause problems in initial_cost_mergejoin() where we perform some calculations based on thos

pgsql: Relax some asserts in merge join costing code

2020-10-19 Thread David Rowley
Relax some asserts in merge join costing code In the planner, it was possible, given an extreme enough case containing a large number of joins for the number of estimated rows to become infinite. This could cause problems in initial_cost_mergejoin() where we perform some calculations based on thos

pgsql: Relax some asserts in merge join costing code

2020-10-19 Thread David Rowley
Relax some asserts in merge join costing code In the planner, it was possible, given an extreme enough case containing a large number of joins for the number of estimated rows to become infinite. This could cause problems in initial_cost_mergejoin() where we perform some calculations based on thos

pgsql: Relax some asserts in merge join costing code

2020-10-19 Thread David Rowley
Relax some asserts in merge join costing code In the planner, it was possible, given an extreme enough case containing a large number of joins for the number of estimated rows to become infinite. This could cause problems in initial_cost_mergejoin() where we perform some calculations based on thos

pgsql: Relax some asserts in merge join costing code

2020-10-19 Thread David Rowley
Relax some asserts in merge join costing code In the planner, it was possible, given an extreme enough case containing a large number of joins for the number of estimated rows to become infinite. This could cause problems in initial_cost_mergejoin() where we perform some calculations based on thos