SET citus.next_shard_id TO 1670000;
CREATE SCHEMA expression_reference_join;
SET search_path TO expression_reference_join;
SET citus.shard_count TO 4;
SET citus.enable_repartition_joins TO on;
CREATE TABLE ref (a int, b int);
CREATE TABLE test (x int, y int);
INSERT INTO ref VALUES
    (2,2),
    (4,4);
INSERT INTO test VALUES
    (1,2),
    (2,2);
SELECT create_reference_table('ref');
NOTICE:  Copying data from local table...
NOTICE:  copying the data has completed
DETAIL:  The local data in the table is no longer visible, but is still on disk.
HINT:  To remove the local data, run: SELECT truncate_local_data_after_distributing_table($$expression_reference_join.ref$$)
 create_reference_table
---------------------------------------------------------------------

(1 row)

SELECT create_distributed_table('test', 'x');
NOTICE:  Copying data from local table...
NOTICE:  copying the data has completed
DETAIL:  The local data in the table is no longer visible, but is still on disk.
HINT:  To remove the local data, run: SELECT truncate_local_data_after_distributing_table($$expression_reference_join.test$$)
 create_distributed_table
---------------------------------------------------------------------

(1 row)

-- PR 3180 implements expressions in join clauses to reference tables to support CHbenCHmark queries 7/8/9
-- plannable as a repartition + reference join, now with an expression in the join clause
SELECT *
FROM
    test t1 JOIN test t2 USING (y), -- causes repartition, which makes this not routable or pushdownable
    ref a
WHERE t2.y * 2 = a.a
ORDER BY 1,2,3;
 y | x | x | a | b
---------------------------------------------------------------------
 2 | 1 | 1 | 4 | 4
 2 | 1 | 2 | 4 | 4
 2 | 2 | 1 | 4 | 4
 2 | 2 | 2 | 4 | 4
(4 rows)

-- The join clause is wider than it used to be, causing this query to be
-- recognized by the LogicalPlanner as a repartition join.
-- Due to a three-way join this causes no valid path, besides the cartesian
-- product on reference tables. This is allowed, so it should be able to be
-- planned.
SELECT *
FROM
    test t1 JOIN test t2 USING (y), -- causes repartition, which makes this not routable or pushdownable
    ref a,
    ref b
WHERE t2.y - a.a - b.b = 0
ORDER BY 1,2,3;
 y | x | x | a | b | a | b
---------------------------------------------------------------------
(0 rows)

-- The join clause is wider than it used to be, causing this query to be recognized by the LogicalPlanner as a repartition join.
-- Unplannable query due to a three-way join which causes no valid path to be found
SELECT *
FROM
    test t1 JOIN test t2 USING (y), -- causes repartition, which makes this not routable or pushdownable
    test a,
    test b
WHERE t2.y - a.x - b.x = 0
ORDER BY 1,2,3;
ERROR:  complex joins are only supported when all distributed tables are joined on their distribution columns with equal operator
SET client_min_messages TO WARNING;
DROP SCHEMA expression_reference_join CASCADE;