mirror of https://github.com/citusdata/citus.git
494 lines
22 KiB
Plaintext
494 lines
22 KiB
Plaintext
--
|
|
-- MULTI_ALTER_TABLE_ADD_CONSTRAINTS
|
|
--
|
|
-- Test checks whether constraints of distributed tables can be adjusted using
|
|
-- the ALTER TABLE ... ADD CONSTRAINT ... command.
|
|
ALTER SEQUENCE pg_catalog.pg_dist_shardid_seq RESTART 1450000;
|
|
ALTER SEQUENCE pg_catalog.pg_dist_jobid_seq RESTART 1450000;
|
|
-- Check "PRIMARY KEY CONSTRAINT"
|
|
CREATE TABLE products (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products', 'product_no');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can only add primary key constraint on distribution column (or group of columns
|
|
-- including distribution column)
|
|
-- Command below should error out since 'name' is not a distribution column
|
|
ALTER TABLE products ADD CONSTRAINT p_key PRIMARY KEY(name);
|
|
ERROR: cannot create constraint on "products"
|
|
DETAIL: Distributed relations cannot have UNIQUE, EXCLUDE, or PRIMARY KEY constraints that do not include the partition column (with an equality operator if EXCLUDE).
|
|
ALTER TABLE products ADD CONSTRAINT p_key PRIMARY KEY(product_no);
|
|
NOTICE: using one-phase commit for distributed DDL commands
|
|
HINT: You can enable two-phase commit for extra safety with: SET citus.multi_shard_commit_protocol TO '2pc'
|
|
INSERT INTO products VALUES(1, 'product_1', 1);
|
|
-- Should error out, since we are trying to add a new row having a value on p_key column
|
|
-- conflicting with the existing row.
|
|
INSERT INTO products VALUES(1, 'product_1', 1);
|
|
ERROR: duplicate key value violates unique constraint "p_key_1450001"
|
|
DETAIL: Key (product_no)=(1) already exists.
|
|
CONTEXT: while executing command on localhost:57638
|
|
ALTER TABLE products DROP CONSTRAINT p_key;
|
|
INSERT INTO products VALUES(1, 'product_1', 1);
|
|
-- Can not create constraint since it conflicts with the existing data
|
|
ALTER TABLE products ADD CONSTRAINT p_key PRIMARY KEY(product_no);
|
|
ERROR: could not create unique index "p_key_1450001"
|
|
DETAIL: Key (product_no)=(1) is duplicated.
|
|
CONTEXT: while executing command on localhost:57637
|
|
DROP TABLE products;
|
|
-- Check "PRIMARY KEY CONSTRAINT" with reference table
|
|
CREATE TABLE products_ref (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_reference_table('products_ref');
|
|
create_reference_table
|
|
------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can add PRIMARY KEY to any column
|
|
ALTER TABLE products_ref ADD CONSTRAINT p_key PRIMARY KEY(name);
|
|
ALTER TABLE products_ref DROP CONSTRAINT p_key;
|
|
ALTER TABLE products_ref ADD CONSTRAINT p_key PRIMARY KEY(product_no);
|
|
INSERT INTO products_ref VALUES(1, 'product_1', 1);
|
|
-- Should error out, since we are trying to add new row having a value on p_key column
|
|
-- conflicting with the existing row.
|
|
INSERT INTO products_ref VALUES(1, 'product_1', 1);
|
|
ERROR: duplicate key value violates unique constraint "p_key_1450032"
|
|
DETAIL: Key (product_no)=(1) already exists.
|
|
CONTEXT: while executing command on localhost:57637
|
|
DROP TABLE products_ref;
|
|
-- Check "PRIMARY KEY CONSTRAINT" on append table
|
|
CREATE TABLE products_append (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products_append', 'product_no', 'append');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can only add primary key constraint on distribution column (or group
|
|
-- of columns including distribution column)
|
|
-- Command below should error out since 'name' is not a distribution column
|
|
ALTER TABLE products_append ADD CONSTRAINT p_key_name PRIMARY KEY(name);
|
|
WARNING: table "products_append" has a UNIQUE or EXCLUDE constraint
|
|
DETAIL: UNIQUE constraints, EXCLUDE constraints, and PRIMARY KEYs on append-partitioned tables cannot be enforced.
|
|
HINT: Consider using hash partitioning.
|
|
ERROR: cannot create constraint on "products_append"
|
|
DETAIL: Distributed relations cannot have UNIQUE, EXCLUDE, or PRIMARY KEY constraints that do not include the partition column (with an equality operator if EXCLUDE).
|
|
ALTER TABLE products_append ADD CONSTRAINT p_key PRIMARY KEY(product_no);
|
|
WARNING: table "products_append" has a UNIQUE or EXCLUDE constraint
|
|
DETAIL: UNIQUE constraints, EXCLUDE constraints, and PRIMARY KEYs on append-partitioned tables cannot be enforced.
|
|
HINT: Consider using hash partitioning.
|
|
--- Error out since first and third rows have the same product_no
|
|
\COPY products_append FROM STDIN DELIMITER AS ',';
|
|
ERROR: duplicate key value violates unique constraint "p_key_1450033"
|
|
DETAIL: Key (product_no)=(1) already exists.
|
|
DROP TABLE products_append;
|
|
-- Check "UNIQUE CONSTRAINT"
|
|
CREATE TABLE unique_test_table(id int, name varchar(20));
|
|
SELECT create_distributed_table('unique_test_table', 'id');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can only add unique constraint on distribution column (or group
|
|
-- of columns including distribution column)
|
|
-- Command below should error out since 'name' is not a distribution column
|
|
ALTER TABLE unique_test_table ADD CONSTRAINT unn_name UNIQUE(name);
|
|
ERROR: cannot create constraint on "unique_test_table"
|
|
DETAIL: Distributed relations cannot have UNIQUE, EXCLUDE, or PRIMARY KEY constraints that do not include the partition column (with an equality operator if EXCLUDE).
|
|
ALTER TABLE unique_test_table ADD CONSTRAINT unn_id UNIQUE(id);
|
|
-- Error out, since table can not have two rows with same id.
|
|
INSERT INTO unique_test_table VALUES(1, 'Ahmet');
|
|
INSERT INTO unique_test_table VALUES(1, 'Mehmet');
|
|
ERROR: duplicate key value violates unique constraint "unn_id_1450035"
|
|
DETAIL: Key (id)=(1) already exists.
|
|
CONTEXT: while executing command on localhost:57638
|
|
ALTER TABLE unique_test_table DROP CONSTRAINT unn_id;
|
|
-- Insert row which will conflict with the next unique constraint command
|
|
INSERT INTO unique_test_table VALUES(1, 'Mehmet');
|
|
-- Can not create constraint since it conflicts with the existing data
|
|
ALTER TABLE unique_test_table ADD CONSTRAINT unn_id UNIQUE(id);
|
|
ERROR: could not create unique index "unn_id_1450035"
|
|
DETAIL: Key (id)=(1) is duplicated.
|
|
CONTEXT: while executing command on localhost:57637
|
|
-- Can create unique constraint over multiple columns which must include
|
|
-- distribution column
|
|
ALTER TABLE unique_test_table ADD CONSTRAINT unn_id_name UNIQUE(id, name);
|
|
-- Error out, since tables can not have two rows with same id and name.
|
|
INSERT INTO unique_test_table VALUES(1, 'Mehmet');
|
|
ERROR: duplicate key value violates unique constraint "unn_id_name_1450035"
|
|
DETAIL: Key (id, name)=(1, Mehmet) already exists.
|
|
CONTEXT: while executing command on localhost:57638
|
|
DROP TABLE unique_test_table;
|
|
-- Check "UNIQUE CONSTRAINT" with reference table
|
|
CREATE TABLE unique_test_table_ref(id int, name varchar(20));
|
|
SELECT create_reference_table('unique_test_table_ref');
|
|
create_reference_table
|
|
------------------------
|
|
|
|
(1 row)
|
|
|
|
-- We can add unique constraint on any column with reference tables
|
|
ALTER TABLE unique_test_table_ref ADD CONSTRAINT unn_name UNIQUE(name);
|
|
ALTER TABLE unique_test_table_ref ADD CONSTRAINT unn_id UNIQUE(id);
|
|
-- Error out. Since the table can not have two rows with the same id.
|
|
INSERT INTO unique_test_table_ref VALUES(1, 'Ahmet');
|
|
INSERT INTO unique_test_table_ref VALUES(1, 'Mehmet');
|
|
ERROR: duplicate key value violates unique constraint "unn_id_1450066"
|
|
DETAIL: Key (id)=(1) already exists.
|
|
CONTEXT: while executing command on localhost:57637
|
|
-- We can add unique constraint with multiple columns
|
|
ALTER TABLE unique_test_table_ref DROP CONSTRAINT unn_id;
|
|
ALTER TABLE unique_test_table_ref ADD CONSTRAINT unn_id_name UNIQUE(id,name);
|
|
-- Error out, since two rows can not have the same id or name.
|
|
INSERT INTO unique_test_table_ref VALUES(1, 'Mehmet');
|
|
DROP TABLE unique_test_table_ref;
|
|
-- Check "UNIQUE CONSTRAINT" with append table
|
|
CREATE TABLE unique_test_table_append(id int, name varchar(20));
|
|
SELECT create_distributed_table('unique_test_table_append', 'id', 'append');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can only add unique constraint on distribution column (or group
|
|
-- of columns including distribution column)
|
|
-- Command below should error out since 'name' is not a distribution column
|
|
ALTER TABLE unique_test_table_append ADD CONSTRAINT unn_name UNIQUE(name);
|
|
WARNING: table "unique_test_table_append" has a UNIQUE or EXCLUDE constraint
|
|
DETAIL: UNIQUE constraints, EXCLUDE constraints, and PRIMARY KEYs on append-partitioned tables cannot be enforced.
|
|
HINT: Consider using hash partitioning.
|
|
ERROR: cannot create constraint on "unique_test_table_append"
|
|
DETAIL: Distributed relations cannot have UNIQUE, EXCLUDE, or PRIMARY KEY constraints that do not include the partition column (with an equality operator if EXCLUDE).
|
|
ALTER TABLE unique_test_table_append ADD CONSTRAINT unn_id UNIQUE(id);
|
|
WARNING: table "unique_test_table_append" has a UNIQUE or EXCLUDE constraint
|
|
DETAIL: UNIQUE constraints, EXCLUDE constraints, and PRIMARY KEYs on append-partitioned tables cannot be enforced.
|
|
HINT: Consider using hash partitioning.
|
|
-- Error out. Table can not have two rows with the same id.
|
|
\COPY unique_test_table_append FROM STDIN DELIMITER AS ',';
|
|
ERROR: duplicate key value violates unique constraint "unn_id_1450067"
|
|
DETAIL: Key (id)=(1) already exists.
|
|
DROP TABLE unique_test_table_append;
|
|
-- Check "CHECK CONSTRAINT"
|
|
CREATE TABLE products (
|
|
product_no integer,
|
|
name text,
|
|
price numeric,
|
|
discounted_price numeric
|
|
);
|
|
SELECT create_distributed_table('products', 'product_no');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can add column and table check constraints
|
|
ALTER TABLE products ADD CONSTRAINT p_check CHECK(price > 0);
|
|
ALTER TABLE products ADD CONSTRAINT p_multi_check CHECK(price > discounted_price);
|
|
-- First and third queries will error out, because of conflicts with p_check and
|
|
-- p_multi_check, respectively.
|
|
INSERT INTO products VALUES(1, 'product_1', -1, -2);
|
|
ERROR: new row for relation "products_1450069" violates check constraint "p_check_1450069"
|
|
DETAIL: Failing row contains (1, product_1, -1, -2).
|
|
CONTEXT: while executing command on localhost:57638
|
|
INSERT INTO products VALUES(1, 'product_1', 5, 3);
|
|
INSERT INTO products VALUES(1, 'product_1', 2, 3);
|
|
ERROR: new row for relation "products_1450069" violates check constraint "p_multi_check_1450069"
|
|
DETAIL: Failing row contains (1, product_1, 2, 3).
|
|
CONTEXT: while executing command on localhost:57638
|
|
DROP TABLE products;
|
|
-- Check "CHECK CONSTRAINT" with reference table
|
|
CREATE TABLE products_ref (
|
|
product_no integer,
|
|
name text,
|
|
price numeric,
|
|
discounted_price numeric
|
|
);
|
|
SELECT create_reference_table('products_ref');
|
|
create_reference_table
|
|
------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can add column and table check constraints
|
|
ALTER TABLE products_ref ADD CONSTRAINT p_check CHECK(price > 0);
|
|
ALTER TABLE products_ref ADD CONSTRAINT p_multi_check CHECK(price > discounted_price);
|
|
-- First and third queries will error out, because of conflicts with p_check and
|
|
-- p_multi_check, respectively.
|
|
INSERT INTO products_ref VALUES(1, 'product_1', -1, -2);
|
|
ERROR: new row for relation "products_ref_1450100" violates check constraint "p_check_1450100"
|
|
DETAIL: Failing row contains (1, product_1, -1, -2).
|
|
CONTEXT: while executing command on localhost:57637
|
|
INSERT INTO products_ref VALUES(1, 'product_1', 5, 3);
|
|
INSERT INTO products_ref VALUES(1, 'product_1', 2, 3);
|
|
ERROR: new row for relation "products_ref_1450100" violates check constraint "p_multi_check_1450100"
|
|
DETAIL: Failing row contains (1, product_1, 2, 3).
|
|
CONTEXT: while executing command on localhost:57637
|
|
DROP TABLE products_ref;
|
|
-- Check "CHECK CONSTRAINT" with append table
|
|
CREATE TABLE products_append (
|
|
product_no int,
|
|
name varchar(20),
|
|
price int,
|
|
discounted_price int
|
|
);
|
|
SELECT create_distributed_table('products_append', 'product_no', 'append');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can add column and table check constraints
|
|
ALTER TABLE products_append ADD CONSTRAINT p_check CHECK(price > 0);
|
|
ALTER TABLE products_append ADD CONSTRAINT p_multi_check CHECK(price > discounted_price);
|
|
-- Error out,since the third row conflicting with the p_multi_check
|
|
\COPY products_append FROM STDIN DELIMITER AS ',';
|
|
ERROR: new row for relation "products_append_1450101" violates check constraint "p_multi_check"
|
|
DETAIL: Failing row contains (1, Product_3, 8, 10).
|
|
DROP TABLE products_append;
|
|
-- Check "EXCLUSION CONSTRAINT"
|
|
CREATE TABLE products (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products', 'product_no');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can only add exclusion constraint on distribution column (or group of columns
|
|
-- including distribution column)
|
|
-- Command below should error out since 'name' is not a distribution column
|
|
ALTER TABLE products ADD CONSTRAINT exc_name EXCLUDE USING btree (name with =);
|
|
ERROR: cannot create constraint on "products"
|
|
DETAIL: Distributed relations cannot have UNIQUE, EXCLUDE, or PRIMARY KEY constraints that do not include the partition column (with an equality operator if EXCLUDE).
|
|
-- We can add composite exclusion
|
|
ALTER TABLE products ADD CONSTRAINT exc_pno_name EXCLUDE USING btree (product_no with =, name with =);
|
|
-- 4th command will error out since it conflicts with exc_pno_name constraint
|
|
INSERT INTO products VALUES(1,'product_1', 5);
|
|
INSERT INTO products VALUES(1,'product_2', 10);
|
|
INSERT INTO products VALUES(2,'product_2', 5);
|
|
INSERT INTO products VALUES(2,'product_2', 5);
|
|
ERROR: conflicting key value violates exclusion constraint "exc_pno_name_1450126"
|
|
DETAIL: Key (product_no, name)=(2, product_2) conflicts with existing key (product_no, name)=(2, product_2).
|
|
CONTEXT: while executing command on localhost:57637
|
|
DROP TABLE products;
|
|
-- Check "EXCLUSION CONSTRAINT" with reference table
|
|
CREATE TABLE products_ref (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_reference_table('products_ref');
|
|
create_reference_table
|
|
------------------------
|
|
|
|
(1 row)
|
|
|
|
-- We can add exclusion constraint on any column
|
|
ALTER TABLE products_ref ADD CONSTRAINT exc_name EXCLUDE USING btree (name with =);
|
|
-- We can add composite exclusion because none of pair of rows are conflicting
|
|
ALTER TABLE products_ref ADD CONSTRAINT exc_pno_name EXCLUDE USING btree (product_no with =, name with =);
|
|
-- Third insertion will error out, since it has the same name with second insertion
|
|
INSERT INTO products_ref VALUES(1,'product_1', 5);
|
|
INSERT INTO products_ref VALUES(1,'product_2', 10);
|
|
INSERT INTO products_ref VALUES(2,'product_2', 5);
|
|
ERROR: conflicting key value violates exclusion constraint "exc_name_1450134"
|
|
DETAIL: Key (name)=(product_2) conflicts with existing key (name)=(product_2).
|
|
CONTEXT: while executing command on localhost:57637
|
|
DROP TABLE products_ref;
|
|
-- Check "EXCLUSION CONSTRAINT" with append table
|
|
CREATE TABLE products_append (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products_append', 'product_no','append');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Can only add exclusion constraint on distribution column (or group of column
|
|
-- including distribution column)
|
|
-- Command below should error out since 'name' is not a distribution column
|
|
ALTER TABLE products_append ADD CONSTRAINT exc_name EXCLUDE USING btree (name with =);
|
|
WARNING: table "products_append" has a UNIQUE or EXCLUDE constraint
|
|
DETAIL: UNIQUE constraints, EXCLUDE constraints, and PRIMARY KEYs on append-partitioned tables cannot be enforced.
|
|
HINT: Consider using hash partitioning.
|
|
ERROR: cannot create constraint on "products_append"
|
|
DETAIL: Distributed relations cannot have UNIQUE, EXCLUDE, or PRIMARY KEY constraints that do not include the partition column (with an equality operator if EXCLUDE).
|
|
ALTER TABLE products_append ADD CONSTRAINT exc_pno_name EXCLUDE USING btree (product_no with =, name with =);
|
|
WARNING: table "products_append" has a UNIQUE or EXCLUDE constraint
|
|
DETAIL: UNIQUE constraints, EXCLUDE constraints, and PRIMARY KEYs on append-partitioned tables cannot be enforced.
|
|
HINT: Consider using hash partitioning.
|
|
-- Error out since first and third can not pass the exclusion check.
|
|
\COPY products_append FROM STDIN DELIMITER AS ',';
|
|
ERROR: conflicting key value violates exclusion constraint "exc_pno_name_1450135"
|
|
DETAIL: Key (product_no, name)=(1, Product_1) conflicts with existing key (product_no, name)=(1, Product_1).
|
|
DROP TABLE products_append;
|
|
-- Check "NOT NULL"
|
|
CREATE TABLE products (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products', 'product_no');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
ALTER TABLE products ALTER COLUMN name SET NOT NULL;
|
|
-- Insertions will error out since both product_no and name can not have NULL value
|
|
INSERT INTO products VALUES(1,NULL,5);
|
|
ERROR: null value in column "name" violates not-null constraint
|
|
DETAIL: Failing row contains (1, null, 5).
|
|
CONTEXT: while executing command on localhost:57638
|
|
INSERT INTO products VALUES(NULL,'product_1', 5);
|
|
ERROR: cannot perform an INSERT with NULL in the partition column
|
|
DROP TABLE products;
|
|
-- Check "NOT NULL" with reference table
|
|
CREATE TABLE products_ref (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_reference_table('products_ref');
|
|
create_reference_table
|
|
------------------------
|
|
|
|
(1 row)
|
|
|
|
ALTER TABLE products_ref ALTER COLUMN name SET NOT NULL;
|
|
-- Insertions will error out since both product_no and name can not have NULL value
|
|
INSERT INTO products_ref VALUES(1,NULL,5);
|
|
ERROR: null value in column "name" violates not-null constraint
|
|
DETAIL: Failing row contains (1, null, 5).
|
|
CONTEXT: while executing command on localhost:57637
|
|
INSERT INTO products_ref VALUES(NULL,'product_1', 5);
|
|
DROP TABLE products_ref;
|
|
-- Check "NOT NULL" with append table
|
|
CREATE TABLE products_append (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products_append', 'product_no', 'append');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
ALTER TABLE products_append ALTER COLUMN name SET NOT NULL;
|
|
-- Error out since name and product_no columns can not handle NULL value.
|
|
\COPY products_append FROM STDIN DELIMITER AS ',';
|
|
DROP TABLE products_append;
|
|
-- Tests for ADD CONSTRAINT is not only subcommand
|
|
CREATE TABLE products (
|
|
product_no integer,
|
|
name text,
|
|
price numeric
|
|
);
|
|
SELECT create_distributed_table('products', 'product_no');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
-- Should error out since add constraint is not the single subcommand
|
|
ALTER TABLE products ADD CONSTRAINT unn_1 UNIQUE(product_no, price), ADD CONSTRAINT unn_2 UNIQUE(product_no, name);
|
|
ERROR: cannot execute ADD CONSTRAINT command with other subcommands
|
|
HINT: You can issue each subcommand separately
|
|
-- Tests for constraints without name
|
|
-- Commands below should error out since constraints do not have the name
|
|
ALTER TABLE products ADD UNIQUE(product_no);
|
|
ERROR: cannot create constraint without a name on a distributed table
|
|
ALTER TABLE products ADD PRIMARY KEY(product_no);
|
|
ERROR: cannot create constraint without a name on a distributed table
|
|
ALTER TABLE products ADD CHECK(product_no <> 0);
|
|
ERROR: cannot create constraint without a name on a distributed table
|
|
ALTER TABLE products ADD EXCLUDE USING btree (product_no with =);
|
|
ERROR: cannot create constraint without a name on a distributed table
|
|
DROP TABLE products;
|
|
-- Tests with transactions
|
|
CREATE TABLE products (
|
|
product_no integer,
|
|
name text,
|
|
price numeric,
|
|
discounted_price numeric
|
|
);
|
|
SELECT create_distributed_table('products', 'product_no');
|
|
create_distributed_table
|
|
--------------------------
|
|
|
|
(1 row)
|
|
|
|
BEGIN;
|
|
INSERT INTO products VALUES(1,'product_1', 5);
|
|
-- Should error out since conflicts with the above single-shard data modification command.
|
|
ALTER TABLE products ADD CONSTRAINT unn_pno UNIQUE(product_no);
|
|
ERROR: distributed DDL commands must not appear within transaction blocks containing single-shard data modifications
|
|
ROLLBACK;
|
|
BEGIN;
|
|
-- Add constraints
|
|
ALTER TABLE products ADD CONSTRAINT unn_pno UNIQUE(product_no);
|
|
ALTER TABLE products ADD CONSTRAINT check_price CHECK(price > discounted_price);
|
|
ALTER TABLE products ALTER COLUMN product_no SET NOT NULL;
|
|
ALTER TABLE products ADD CONSTRAINT p_key_product PRIMARY KEY(product_no);
|
|
-- Single shard DML command can't be located in the same transaction with above commands.
|
|
INSERT INTO products VALUES(1,'product_1', 10, 8);
|
|
ERROR: single-shard DML commands must not appear in transaction blocks which contain multi-shard data modifications
|
|
ROLLBACK;
|
|
-- There should be no constraint on master and worker(s)
|
|
\d products
|
|
Table "public.products"
|
|
Column | Type | Modifiers
|
|
------------------+---------+-----------
|
|
product_no | integer |
|
|
name | text |
|
|
price | numeric |
|
|
discounted_price | numeric |
|
|
|
|
\c - - - :worker_1_port
|
|
\d products_1450199
|
|
\c - - - :master_port
|
|
-- Tests to check the effect of rollback
|
|
BEGIN;
|
|
-- Add constraints (which will be rollbacked)
|
|
ALTER TABLE products ADD CONSTRAINT unn_pno UNIQUE(product_no);
|
|
NOTICE: using one-phase commit for distributed DDL commands
|
|
HINT: You can enable two-phase commit for extra safety with: SET citus.multi_shard_commit_protocol TO '2pc'
|
|
ALTER TABLE products ADD CONSTRAINT check_price CHECK(price > discounted_price);
|
|
ALTER TABLE products ADD CONSTRAINT p_key_product PRIMARY KEY(product_no);
|
|
ROLLBACK;
|
|
-- There should be no constraint on master and worker(s)
|
|
\d products
|
|
Table "public.products"
|
|
Column | Type | Modifiers
|
|
------------------+---------+-----------
|
|
product_no | integer |
|
|
name | text |
|
|
price | numeric |
|
|
discounted_price | numeric |
|
|
|
|
\c - - - :worker_1_port
|
|
\d products_1450199
|
|
\c - - - :master_port
|
|
DROP TABLE products;
|