citus

Commit Graph

Author	SHA1	Message	Date
Jelte Fennema	acd12a6de5	Normalize tests: s/read_intermediate_result\('[0-9]+_/read_intermediate_result('XXX_/g	2020-01-06 09:32:03 +01:00
Jelte Fennema	21dbd4e55d	Normalize tests: s/generating subplan [0-9]+\_/generating subplan XXX\_/g	2020-01-06 09:32:03 +01:00
Jelte Fennema	58723dd8b0	Normalize tests: s/DEBUG: Plan [0-9]+/DEBUG: Plan XXX/g	2020-01-06 09:32:03 +01:00
Jelte Fennema	7730bd449c	Normalize tests: Remove trailing whitespace	2020-01-06 09:32:03 +01:00
Jelte Fennema	7f3de68b0d	Normalize tests: header separator length	2020-01-06 09:32:03 +01:00
Onder Kalaci	04d9e886fe	Run concurrent modification queries in tests sequentially	2018-05-10 11:59:18 +03:00
Hadi Moshayedi	86b12bc2d0	Always prefix operators with their namespace. (#2147 ) Previously we checked if an operator is in pg_catalog, and if it wasn't we prefixed it with namespace in worker queries. This can have a huge impact on performance of physical planner when using custom data types. This happened regardless of current search_path config, because Citus overrides the search path in get_query_def_extended(). When we do so, the check for existence of the operator in current search path in generate_operator_name() fails for any operators outside pg_catalog. This means that nothing gets cached, and in the following calls we will again recheck the system tables for existence of the operators, which took an additional 40-50ms for some of the usecases we were seeing. In this change we skip the pg_catalog check, and always prefix the operator with its namespace.	2018-05-05 13:27:26 -04:00
Marco Slot	09c09f650f	Recursively plan set operations when leaf nodes recur	2017-12-26 13:46:55 +02:00

8 Commits (acd12a6de5fa20e3b9fe1d133db7467a7cdd55fc)