Accept regression diffs in update test case

The first diff was in fact a mistake and the actual output matched with the
upstream output. It must have been missed during the merge process. The other
diff was simply an error because XL doesn't allow updating distribution key
column.

diff --git a/src/test/regress/expected/update.out b/src/test/regress/expected/update.out
index a9796445b3843791b4fd76b48e1841b0730a1725..f761e47e80800aff918b4d3ffc3a729b14f66b48 100644 (file)
--- a/src/test/regress/expected/update.out
+++ b/src/test/regress/expected/update.out
@@ -161,7 +161,7 @@ UPDATE update_test SET c = repeat('x', 10000) WHERE c = 'car';
 SELECT a, b, char_length(c) FROM update_test ORDER BY a;
  a  |  b  | char_length 
 ----+-----+-------------
- 21 | 101 |            
+ 21 | 100 |            
  41 |  12 |       10000
  42 |  12 |       10000
     |     |            
@@ -211,8 +211,8 @@ insert into part_a_1_a_10 values ('a', 1);
 insert into part_b_10_b_20 values ('b', 10);
 -- fail
 update part_a_1_a_10 set a = 'b' where a = 'a';
-ERROR:  new row for relation "part_a_1_a_10" violates partition constraint
-DETAIL:  Failing row contains (b, 1).
+ERROR:  could not plan this distributed update
+DETAIL:  correlated UPDATE or updating distribution column currently not supported in Postgres-XL.
 update range_parted set b = b - 1 where b = 10;
 ERROR:  new row for relation "part_b_10_b_20" violates partition constraint
 DETAIL:  Failing row contains (b, 9).