Chris Browne cbbrowne at lists.slony.info
Thu Apr 30 10:04:39 PDT 2009
Update of /home/cvsd/slony1/slony1-www/content
In directory main.slony.info:/tmp/cvs-serv8141/content

Modified Files:
	news.txt 
Log Message:
Add 2.0.2 release candidate notes


Index: news.txt
===================================================================
RCS file: /home/cvsd/slony1/slony1-www/content/news.txt,v
retrieving revision 1.55
retrieving revision 1.56
diff -C2 -d -r1.55 -r1.56
*** news.txt	30 Apr 2009 16:38:09 -0000	1.55
--- news.txt	30 Apr 2009 17:04:37 -0000	1.56
***************
*** 15,18 ****
--- 15,72 ----
  
  ---
+ Slony-I 2.0.2 release candidate released
+ http://main.slony.info/downloads/2.0/source/slony1-2.0.2-rc.tar.bz2
+ 2009-04-30
+ Chris Browne
+ 
+ The release candidate <a href=
+ "http://main.slony.info/downloads/2.0/source/slony1-2.0.2-rc.tar.bz2">
+ slony1-2.0.2-rc.tar.bz2 </a> has been generated.
+ 
+ <ul>
+ <li> PostgreSQL 8.4 compatibility - src/backend/slony1_funcs.c needed to
+   #include "catalog/pg_type.h"; that is no longer implicitly included by
+   the SPI #include
+ 
+ <li> Fix bug #71 - config dump was failing on string entries that were NULL
+ 
+ <li> Fix bug #76 - REPAIR CONFIG could have collisions where, when we 
+   load a schema, one entry in sl_table already has an OID value
+   that incorrectly matches a value that another update is trying to
+   fix.
+ 
+ <P>  This would cause REPAIR CONFIG to fail.
+ 
+ <P>  Put in a query that updates the oids in sl_table and sl_sequence to
+   randomly selected values from pg_class that couldn't match (since
+   the values selected are from non-table/non-sequence objects)
+ 
+ <li> Updated release notes to indicate that 2.0 only supports PostgreSQL
+   8.3+
+ 
+ <li> Change to configure.ac to allow it to run on autoconf 2.63; there was
+   something unsuitable about SLONREL_VERSION processing
+ 
+ <li> Fixes to Makefile for admin guide
+ 
+ <li> Various fixes to admin guide material
+ 
+ <li> Added an extra test to Schema name test that validates that things
+   can operate properly even if the DB lacks a "public" schema
+ 
+ <li> Fixed bug in tools/start_slon.sh
+ 
+ <li> Fixed pathname substitutions in a couple of altperl scripts
+ 
+ <li> Add a test which validates that the cluster schema name is valid; 
+   pgAdminIII allowed setting up cluster names that slonik would refuse
+   to connect to.
+ 
+ <li> Revised regression tests to use SYNC/WAIT FOR EVENT instead of
+   queries that try to coordinate sl_status information with rather
+   less determinacy...
+ 
+ </ul>
+ ---
  Slony-I 1.2.16 release candidate released
  http://main.slony.info/downloads/1.2/source/slony1-1.2.16-rc.tar.bz2



More information about the Slony1-commit mailing list