Update cmin values in combocid based on XL 9.5

As mentioned in 3a64cfdde3, some of the output differences (compared
to PostgreSQL 10) may be caused by XL advancing cmin more often, for
example due to splitting a single command into multiple steps.

So tweak the expected output using output from Postgres-XL 9.5r1.6.

diff --git a/src/test/regress/expected/combocid.out b/src/test/regress/expected/combocid.out
index ddfd95a6004cf8c60baa73d294105e47b7deae04..9b9f27b38e3b58854f82f0a7ea31922fd128072e 100644 (file)
--- a/src/test/regress/expected/combocid.out
+++ b/src/test/regress/expected/combocid.out
@@ -60,8 +60,8 @@ DELETE FROM combocidtest;
 FETCH ALL FROM c;
  ctid  | cmin | foobar 
 -------+------+--------
- (0,3) |    1 |     11
- (0,4) |    1 |     12
+ (0,3) |    2 |     11
+ (0,4) |    2 |     12
  (0,5) |    0 |    333
 (3 rows)
 
@@ -69,8 +69,8 @@ ROLLBACK;
 SELECT ctid,cmin,* FROM combocidtest ORDER BY ctid;
  ctid  | cmin | foobar 
 -------+------+--------
- (0,3) |    1 |     11
- (0,4) |    1 |     12
+ (0,3) |    2 |     11
+ (0,4) |    2 |     12
 (2 rows)
 
 -- check behavior with locked tuples
@@ -90,8 +90,8 @@ INSERT INTO combocidtest VALUES (444);
 SELECT ctid,cmin,* FROM combocidtest ORDER BY ctid;
  ctid  | cmin | foobar 
 -------+------+--------
- (0,3) |    1 |     11
- (0,4) |    1 |     12
+ (0,3) |    2 |     11
+ (0,4) |    2 |     12
  (0,6) |   10 |    444
 (3 rows)
 
@@ -100,16 +100,16 @@ SELECT ctid,cmin,* FROM combocidtest ORDER BY ctid;
 SELECT ctid,cmin,* FROM combocidtest FOR UPDATE;
  ctid  | cmin | foobar 
 -------+------+--------
- (0,3) |    1 |     11
- (0,4) |    1 |     12
+ (0,3) |    2 |     11
+ (0,4) |    2 |     12
  (0,6) |   10 |    444
 (3 rows)
 
 SELECT ctid,cmin,* FROM combocidtest ORDER BY ctid;
  ctid  | cmin | foobar 
 -------+------+--------
- (0,3) |    1 |     11
- (0,4) |    1 |     12
+ (0,3) |    2 |     11
+ (0,4) |    2 |     12
  (0,6) |   10 |    444
 (3 rows)