citus

Commit Graph

Author	SHA1	Message	Date
Marco Slot	09c09f650f	Recursively plan set operations when leaf nodes recur	2017-12-26 13:46:55 +02:00
Murat Tuncer	87c6f306f1	Fix join clause eq restrictions (#1884 ) We used to error out if the join clause includes filters like t1.a < t2.a even if other filter like t1.key = t2.key exists. Recently we lifted that restriction in subquery planning by not lifting that restriction and focusing on equivalance classes provided by postgres. This checkin forwards previously erroring out real-time queries due to join clauses to subquery planner and let it handle the join even if the query does not have a subquery. We are now pushing down queries that do not have any subqueries in it. Error message looked misleading, changed to a more descriptive one.	2017-12-22 12:16:14 +03:00
Onder Kalaci	e2a5124830	Add regression tests for recursive subquery planning	2017-12-21 08:37:40 +02:00
Marco Slot	ea6b98fda4	Allow count(distinct) in queries with a subquery	2017-12-15 15:24:26 +01:00
Marco Slot	3a4d5f8182	Remove filter checks on leaf queries	2017-11-30 12:25:14 +01:00
Marco Slot	0ad39b36fe	Treat immutable table functions and constant subqueries as reference tables	2017-11-21 14:15:22 +01:00
Marco Slot	89eb833375	Use citus.next_shard_id where practical in regression tests	2017-11-15 10:12:05 +01:00
Jason Petersen	50501227e9	Add ORDER clause to subquery test missing it	2017-06-08 18:30:14 -06:00
Onder Kalaci	df494c0403	Improve subquery pushdown regression tests - Use native postgres function for composite key btree functions - Move explain tests to multi_explain.sql (get rid of .out _0.out files) - Get rid of input/output files for multi_subquery.sql by moving table creations - Update some comments	2017-05-30 14:05:15 +03:00

9 Commits (09c09f650f80c99d7d3a2e552ab53f7e4a0c1ba1)