8 Commits (907d72e60d4043924f52200b24d281fe7b79f75f)

Author	SHA1	Message	Date
Onur Tirtir	f339450a9d	Phase - I: recursively plan non-recurring relations	2022-12-07 18:27:50 +03:00
aykut-bozkurt	83ef600f27	fix false full join pushdown error check (#6523) ... **Problem**: Currently, we error out if we detect recurring tuples in one side without checking the other side of the join. **Solution**: When one side of the full join consists recurring tuples and the other side consists nonrecurring tuples, we should not pushdown to prevent duplicate results. Otherwise, safe to pushdown.	2022-11-30 14:17:56 +03:00
SaitTalhaNisanci	03832f353c	Drop postgres 11 support	2021-03-25 09:20:28 +03:00
Onder Kalaci	64560b07be	Update regression tests-2 ... In this commit, we're introducing a way to prevent CTE inlining via a GUC. The GUC is used in all the tests where PG 11 and PG 12 tests would diverge otherwise. Note that, in PG 12, the restriction information for CTEs are generated. It means that for some queries involving CTEs, Citus planner (router planner/ pushdown planner) may behave differently. So, via the GUC, we prevent tests to diverge on PG 11 vs PG 12. When we drop PG 11 support, we should get rid of the GUC, and mark relevant ctes as MATERIALIZED, which does the same thing.	2020-01-16 12:28:15 +01:00
Philip Dubé	c563e0825c	Strip trailing whitespace and add final newline (#3186) ... This brings files in line with our editorconfig file	2019-11-21 14:25:37 +01:00
Onder Kalaci	41d8c4030a	Add some more regression tests for outer join pushdown	2019-03-19 11:49:38 +03:00
Onder Kalaci	e2a5124830	Add regression tests for recursive subquery planning	2017-12-21 08:37:40 +02:00
mehmet furkan şahin	5851f71bfb	Add CTE regression tests	2017-12-14 09:32:55 +01:00