Stabilize test_decoding touching with sequences
authorTomas Vondra <tomas.vondra@postgresql.org>
Tue, 8 Mar 2022 17:54:37 +0000 (18:54 +0100)
committerTomas Vondra <tomas.vondra@postgresql.org>
Tue, 8 Mar 2022 18:23:00 +0000 (19:23 +0100)
commita180c2b34de0989269fdb819bff241a249bf5380
tree5485b3d201bfa9ae798279b157364ffa38cb84de
parent54c72eb5e5e63f99f68c054900424724b0570b20
Stabilize test_decoding touching with sequences

Some of the test_decoding regression tests are unstable due to modifying
a sequence. The first increment of a sequence after a checkpoint is
always logged (and thus decoded), which makes the output unpredictable.
The runs are usually much shorter than a checkpoint internal, so these
failures are rare, but we've seen a couple of them on animals that are
either slow or are running with valgrind/clobber cache/...

Fixed by skipping sequence decoding in most tests, with the exception of
the test aimed at testing decoding of sequences.

Reported-by: Amita Kapila
Discussion: https://postgr.es/m/d045f3c2-6cfb-06d3-5540-e63c320df8bc@enterprisedb.com
contrib/test_decoding/expected/ddl.out
contrib/test_decoding/expected/decoding_in_xact.out
contrib/test_decoding/expected/replorigin.out
contrib/test_decoding/expected/rewrite.out
contrib/test_decoding/expected/slot.out
contrib/test_decoding/sql/ddl.sql
contrib/test_decoding/sql/decoding_in_xact.sql
contrib/test_decoding/sql/replorigin.sql
contrib/test_decoding/sql/rewrite.sql
contrib/test_decoding/sql/slot.sql