src/test/regress/expected/exclusion_constraints.out

-- Given a create table specifying a constraint
create table exclusion_constraints_t1(a int, b int, EXCLUDE (a WITH =));
ERROR:  GPDB does not support exclusion constraints.
-- Then we errored out
-- Given a create partition table table specifying a constraint
create table exclusion_constraints_pt1(a int, b int, EXCLUDE (b WITH =)) partition by range(a) (start(1) end(4) every(1));
ERROR:  GPDB does not support exclusion constraints.
-- Then we errored out
-- Given a table without constraints
create table exclusion_constraints_t2(a int, b int);
NOTICE:  Table doesn't have 'DISTRIBUTED BY' clause -- Using column named 'a' as the Apache Cloudberry data distribution key for this table.
HINT:  The 'DISTRIBUTED BY' clause determines the distribution of data. Make sure column(s) chosen are the optimal data distribution key to minimize skew.
-- And we alter table to add constraints
ALTER TABLE exclusion_constraints_t2 ADD CONSTRAINT constraint_on_t2 EXCLUDE USING btree (b WITH =);
ERROR:  GPDB does not support exclusion constraints.
-- Then we errored out