From: Tomas Vondra Date: Sun, 8 Oct 2017 22:01:26 +0000 (+0200) Subject: Update cmin values in combocid based on XL 9.5 X-Git-Tag: XL_10_R1BETA1~108 X-Git-Url: http://git.postgresql.org/gitweb/static/gitweb.js?a=commitdiff_plain;h=2439364eef62ce832709a0c3d44b1eee134909ca;p=postgres-xl.git 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 ddfd95a600..9b9f27b38e 100644 --- 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)