Log Message:
-----------
slony1_dump.sh

1.  The error messages being given when SYNC numbers didn't match
    were really confusing...  Changed it to return much more sensible
    values.

2.  The statement that copied the table to stdout was, at some point,
    lost, causing a loss of data.  Returned that to place.

Modified Files:
--------------
    slony1-engine/tools:
        slony1_dump.sh (r1.6 -> r1.7)

-------------- next part --------------
Index: slony1_dump.sh
===================================================================
RCS file: /usr/local/cvsroot/slony1/slony1-engine/tools/slony1_dump.sh,v
retrieving revision 1.6
retrieving revision 1.7
diff -Ltools/slony1_dump.sh -Ltools/slony1_dump.sh -u -w -r1.6 -r1.7
--- tools/slony1_dump.sh
+++ tools/slony1_dump.sh
@@ -126,7 +126,6 @@
 	return p_seq_id;
 end;
 ' language plpgsql;
-
 -- ---------------------------------------------------------------------------------------
 -- FUNCTION finishTableAfterCopy(table_id)
 -- ---------------------------------------------------------------------------------------
@@ -156,7 +155,7 @@
 
 	if v_row.ssy_seqno <> p_old_seq then
 		raise exception ''Slony-I: set % is on sync %, this archive log expects %'', 
-			p_set_id, p_old_seq, p_new_seq;
+			p_set_id, v_row.ssy_seqno, p_old_seq;
 	end if;
 	raise notice ''Slony-I: Process set % sync % time %'', p_set_id, p_new_seq, p_sync_time;
 
@@ -213,6 +212,7 @@
 	# Get fieldnames...
  	fields=`psql -At -c "select $clname.copyfields($tab);" $dbname`
  	echo "select 'copy $tabname $fields from stdin;';"
+	echo "copy $tabname $fields to stdout;"
  	printf "select '\\\\\\\\.';"
 done