From: | Heikki Linnakangas <heikki(dot)linnakangas(at)iki(dot)fi> |
---|---|
To: | pgsql-committers(at)postgresql(dot)org |
Subject: | pgsql: Add an SSI regression test that tests all interesting permutatio |
Date: | 2011-08-18 14:10:45 |
Message-ID: | E1Qu3Iz-0000Qm-AH@gemulon.postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-committers |
Add an SSI regression test that tests all interesting permutations in the
order of begin, prepare, and commit of three concurrent transactions that
have conflicts between them.
The test runs for a quite long time, and the expected output file is huge,
but this test caught some serious bugs during development, so seems
worthwhile to keep. The test uses prepared transactions, so it fails if the
server has max_prepared_transactions=0. Because of that, it's marked as
"ignore" in the schedule file.
Dan Ports
Branch
------
master
Details
-------
http://git.postgresql.org/pg/commitdiff/af35737313f92fcbe227baf51bb69b8650acc41a
Modified Files
--------------
.../isolation/expected/prepared-transactions.out |34843 ++++++++++++++++++++
src/test/isolation/isolation_schedule | 5 +
src/test/isolation/isolationtester.c | 12 +-
.../isolation/specs/prepared-transactions.spec | 1507 +
4 files changed, 36365 insertions(+), 2 deletions(-)
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2011-08-18 15:45:45 | pgsql: Explain max_prepared_transactions requirement in isolation tests |
Previous Message | Robert Haas | 2011-08-18 14:05:14 | pgsql: Make lazy_vacuum_rel call pg_rusage_init only if needed. |