Tue Apr 28 14:48:22 PDT 2009
- Previous message: [Slony1-commit] slony1-engine/tests/testmultiplemoves generate_dml.sh
- Next message: [Slony1-commit] slony1-engine/tests/testschemanames generate_dml.sh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Update of /home/cvsd/slony1/slony1-engine/tests/testpartition In directory main.slony.info:/tmp/cvs-serv6415/testpartition Modified Files: Tag: REL_2_0_STABLE generate_dml.sh Log Message: Revise tests to NOT use poll_cluster to "wait until everything has propagated according to sl_status" - instead, we use SYNC/WAIT FOR EVENT, which submits an event against the origin, and then waits until that specific event has propagated. This means we're testing WAIT FOR EVENT a lot more stringently, and allows tests to run a lot quicker in cases where it takes a while for the nodes to decide they are instantaneously "in sync" Index: generate_dml.sh =================================================================== RCS file: /home/cvsd/slony1/slony1-engine/tests/testpartition/generate_dml.sh,v retrieving revision 1.3 retrieving revision 1.3.2.1 diff -C2 -d -r1.3 -r1.3.2.1 *** generate_dml.sh 11 Apr 2008 15:39:32 -0000 1.3 --- generate_dml.sh 28 Apr 2009 21:48:20 -0000 1.3.2.1 *************** *** 71,75 **** eval port=\$PORT${originnode} # generate_initdata - # No initial data! - launch_poll status "loading data" #$pgbindir/psql -h $host -p $port -d $db -U $user < $mktmp/generate.data 1> $mktmp/initdata.log 2> $mktmp/initdata.log --- 71,74 ----
- Previous message: [Slony1-commit] slony1-engine/tests/testmultiplemoves generate_dml.sh
- Next message: [Slony1-commit] slony1-engine/tests/testschemanames generate_dml.sh
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Slony1-commit mailing list