Update of /home/cvsd/slony1/slony1-engine
In directory main:/tmp/cvs-serv3327

Modified Files:
      Tag: REL_1_2_STABLE
	RELEASE-1.2.7 
Log Message:
Per change committed to HEAD on Jan 30th, this applies to the 1.2 branch

This addresses the problem where a slonik requests UNINSTALL NODE
and this breaks. 

Report in the error message which node it was working on. That way the
gentle user gets an indication as to which node 'broke' if the slonik
script contained multiple such UNINSTALL NODE requests.



Index: RELEASE-1.2.7
===================================================================
RCS file: /home/cvsd/slony1/slony1-engine/Attic/RELEASE-1.2.7,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -C2 -d -r1.1.2.2 -r1.1.2.3
*** RELEASE-1.2.7	2 Feb 2007 22:23:16 -0000	1.1.2.2
--- RELEASE-1.2.7	5 Feb 2007 22:06:52 -0000	1.1.2.3
***************
*** 12,13 ****
--- 12,19 ----
  a logging printf to blow up.  Changed the logging level so that detail
  is only shown at levels 4/5, which won't bite people by default.
+ 
+ - UNINSTALL NODE failures now show node # in slonik error messages
+ 
+ If a user ran several UNINSTALL NODE requests in a single slonik
+ script, and one of them broke, you'd have no ready way to tell which
+ node this failed on.  Added code to report the node # where it failed.