postgresql/src/test/isolation/expected
Alvaro Herrera 54638f5708 Make new isolationtester test more stable
The original coding of the test was relying too much on the ordering in
which backends are awakened once an advisory lock which they wait for is
released.  Change the code so that each backend uses its own advisory
lock instead, so that the output becomes stable.  Also add a few seconds
of sleep between lock releases, so that the test isn't broken in
overloaded buildfarm animals, as suggested by Tom Lane.

Per buildfarm members spoonbill and guaibasaurus.

Discussion: https://www.postgresql.org/message-id/19294.1456551587%40sss.pgh.pa.us
2016-02-29 16:34:56 -03:00
..
aborted-keyrevoke_2.out
aborted-keyrevoke.out
alter-table-1.out
alter-table-2.out
alter-table-3.out
async-notify.out
classroom-scheduling.out
create-trigger.out
deadlock-hard.out
deadlock-simple.out
deadlock-soft-2.out
deadlock-soft.out
delete-abort-savept-2.out
delete-abort-savept.out
drop-index-concurrently-1_2.out
drop-index-concurrently-1.out
eval-plan-qual.out
fk-contention.out
fk-deadlock2_1.out
fk-deadlock2_2.out
fk-deadlock2.out
fk-deadlock_1.out
fk-deadlock.out
index-only-scan.out
insert-conflict-do-nothing.out
insert-conflict-do-update-2.out
insert-conflict-do-update-3.out
insert-conflict-do-update.out
lock-update-delete_1.out
lock-update-delete.out
lock-update-traversal.out
multiple-row-versions.out
multixact-no-deadlock.out
multixact-no-forget_1.out
multixact-no-forget.out
nowait-2.out
nowait-3.out
nowait-4_1.out
nowait-4.out
nowait-5.out
nowait.out
partial-index.out
prepared-transactions.out
project-manager.out
propagate-lock-delete.out
receipt-report.out
referential-integrity.out
ri-trigger.out
simple-write-skew.out
skip-locked-2.out
skip-locked-3.out
skip-locked-4_1.out
skip-locked-4.out
skip-locked.out
temporal-range-integrity.out
timeouts.out
total-cash.out
tuplelock-conflict.out
tuplelock-update.out Make new isolationtester test more stable 2016-02-29 16:34:56 -03:00
two-ids.out