Add materialized view relative triggers case in SingleNode mode.

Triggers like BEFORE/AFTER INSERT/UPDATE/DELETE could be possible
in SingleNode mode because all tables including user tables are
on QD.

An such triiger may change the data of another table who has
relative materialized views.
We should update that views' data status as well.

Add test cases for that.

Authored-by: Zhang Mingli avamingli@gmail.com

Author: avamingli

src/test/singlenode_regress/expected/matview_data.out

@@ -324,10 +324,97 @@ select mvname, datastatus from gp_matview_aux where mvname in ('mv0','mv1', 'mv2
  mv3    | e
 (1 row)
 
+--
+-- Test triggers only for singlenode mode.
+-- All tables are on QD, so triggers could work well, ex
+-- modify another table.
+create table tri_t1(a int, b int);
+create table tri_t2(a int, b int);
+create table tri_t3(a int, b int);
+create materialized view tri_mv1 as select * from tri_t1;
+create materialized view tri_mv2 as select * from tri_t2;
+insert into tri_t3 values (1, 2);
+create materialized view tri_mv3 as select * from tri_t3;
+create function trigger_insert_tri_t2()
+returns trigger AS
+$$
+begin
+  execute 'insert into tri_t2 values(1, 1)';
+  execute 'update tri_t3 set b = 10 where a = 1;';
+  return NEW;
+end;
+$$
+language plpgsql;
+create trigger trigger_insert_tri_t2 before insert ON tri_t1
+  for each row execute procedure trigger_insert_tri_t2();
+select mvname, datastatus from gp_matview_aux where mvname in ('tri_mv1', 'tri_mv2', 'tri_mv3');
+ mvname  | datastatus 
+---------+------------
+ tri_mv1 | u
+ tri_mv2 | u
+ tri_mv3 | u
+(3 rows)
+
+select * from tri_t1;
+ a | b 
+---+---
+(0 rows)
+
+select * from tri_t2;
+ a | b 
+---+---
+(0 rows)
+
+select * from tri_t3;
+ a | b 
+---+---
+ 1 | 2
+(1 row)
+
+insert into tri_t1 values(1, 2);
+select * from tri_t1;
+ a | b 
+---+---
+ 1 | 2
+(1 row)
+
+-- should also insert data
+select * from tri_t2;
+ a | b 
+---+---
+ 1 | 1
+(1 row)
+
+-- shoud be updated
+select * from tri_t3;
+ a | b  
+---+----
+ 1 | 10
+(1 row)
+
+-- check mv status
+select mvname, datastatus from gp_matview_aux where mvname in ('tri_mv1', 'tri_mv2', 'tri_mv3');
+ mvname  | datastatus 
+---------+------------
+ tri_mv2 | i
+ tri_mv3 | e
+ tri_mv1 | i
+(3 rows)
+
+drop trigger trigger_insert_tri_t2 on tri_t1;
+drop function trigger_insert_tri_t2;
+-- start_ignore
 drop schema matview_data_schema cascade;
-NOTICE:  drop cascades to 3 other objects
+NOTICE:  drop cascades to 9 other objects
 DETAIL:  drop cascades to table t2
 drop cascades to table t3
 drop cascades to materialized view mv3
+drop cascades to table tri_t1
+drop cascades to table tri_t2
+drop cascades to table tri_t3
+drop cascades to materialized view tri_mv1
+drop cascades to materialized view tri_mv2
+drop cascades to materialized view tri_mv3
+-- end_ignore
 reset enable_answer_query_using_materialized_views;
 reset optimizer;

src/test/singlenode_regress/sql/matview_data.sql

@@ -114,6 +114,50 @@ drop materialized view mv2;
 drop table t1 cascade;
 select mvname, datastatus from gp_matview_aux where mvname in ('mv0','mv1', 'mv2', 'mv3');
 
+--
+-- Test triggers only for singlenode mode.
+-- All tables are on QD, so triggers could work well, ex
+-- modify another table.
+create table tri_t1(a int, b int);
+create table tri_t2(a int, b int);
+create table tri_t3(a int, b int);
+create materialized view tri_mv1 as select * from tri_t1;
+create materialized view tri_mv2 as select * from tri_t2;
+insert into tri_t3 values (1, 2);
+create materialized view tri_mv3 as select * from tri_t3;
+
+create function trigger_insert_tri_t2()
+returns trigger AS
+$$
+begin
+  execute 'insert into tri_t2 values(1, 1)';
+  execute 'update tri_t3 set b = 10 where a = 1;';
+  return NEW;
+end;
+$$
+language plpgsql;
+
+create trigger trigger_insert_tri_t2 before insert ON tri_t1
+  for each row execute procedure trigger_insert_tri_t2();
+
+select mvname, datastatus from gp_matview_aux where mvname in ('tri_mv1', 'tri_mv2', 'tri_mv3');
+select * from tri_t1;
+select * from tri_t2;
+select * from tri_t3;
+
+insert into tri_t1 values(1, 2);
+select * from tri_t1;
+-- should also insert data
+select * from tri_t2;
+-- shoud be updated
+select * from tri_t3;
+-- check mv status
+select mvname, datastatus from gp_matview_aux where mvname in ('tri_mv1', 'tri_mv2', 'tri_mv3');
+drop trigger trigger_insert_tri_t2 on tri_t1;
+drop function trigger_insert_tri_t2;
+
+-- start_ignore
 drop schema matview_data_schema cascade;
+-- end_ignore
 reset enable_answer_query_using_materialized_views;
 reset optimizer;