Update of /home/cvsd/slony1/slony1-www/content
In directory main.slony.info:/tmp/cvs-serv701/content

Modified Files:
	news.txt 
Log Message:
Updating news to include 2.0.3 and 1.2.21 releases



Index: news.txt
===================================================================
RCS file: /home/cvsd/slony1/slony1-www/content/news.txt,v
retrieving revision 1.67
retrieving revision 1.68
diff -C 2 -d -r1.67 -r1.68
*** news.txt	6 Apr 2010 21:45:52 -0000	1.67
--- news.txt	9 Apr 2010 21:17:51 -0000	1.68
***************
*** 15,24 ****
  
  ---
! Slony-I 1.2.21 RC1 available
! http://main.slony.info/downloads/1.2/source/slony1-1.2.21-rc1.tar.bz2
! 2010-04-06
  Steve Singer
  
! A release candidate for the next minor release of Slony1 1.2.21
  
  <ul>
--- 15,24 ----
  
  ---
! Slony-I 1.2.21  available
! http://main.slony.info/downloads/1.2/source/slony1-1.2.21.tar.bz2
! 2010-04-09
  Steve Singer
  
! The next minor release of Slony1 1.2.21 has been released
  
  <ul>
***************
*** 49,59 ****
  
  ---
! Slony-I 2.0.3 RC4 available
! http://main.slony.info/downloads/2.0/source/slony1-2.0.3-rc4.tar.bz2
! 2010-04-06
  Chris Browne
  
! A fourth release candidate for Slony-I 2.0.3 is now available.  It
! makes the following changes since RC3:
  
  <ul>
--- 49,59 ----
  
  ---
! Slony-I 2.0.3  available
! http://main.slony.info/downloads/2.0/source/slony1-2.0.3.tar.bz2
! 2010-04-09
  Chris Browne
  
! Slony-I 2.0.3 is now available.  It
! makes the following changes since 2.0.2
  
  <ul>
***************
*** 67,71 ****
  
  <li> Quoting problems in Perl script (bug #110)
- 
  <li> Add notes about flex/bison conflict (bug #109)
  
--- 67,70 ----
***************
*** 82,86 ****
  <li> Bug # 113 - DROP cloneNodePrepare since the return type changes.
    Patch from Atte Peltomäki
- 
  <li> Improve configure complaint if it can't find PQunescapeBytea - this
    likely implies that configure couldn't find libpq.
--- 81,84 ----
***************
*** 107,110 ****
--- 105,177 ----
    Eisentraut) - bug #116
  
+ <li>Updates to copyright dates on files
+ 
+ <li>Bug #98 - need WAIT ON parameter in slonik code generated by
+   slonik_move_set altperl script.
+ 
+ <li>Change default $LOGDIR, so that distros won't need to patch it.
+ 
+ <li>Fix LOG_NAME_SUFFIX feature. Thanks to David Fetter and Andrew Dunstan.
+ 
+ <li>Improve documentation on EVENT NODE for STORE NODE command
+ 
+ <li>SLONLOG directory changes for Red Hat-related distributions
+ 
+ <li>Bug #97 - insert into sl_setsync upon FAILOVER had values() clause based on the
+   pre-2.0 schema; fix to use 2.0.
+ 
+ <li>UPGRADE FUNCTIONS failing because functions had their return types changed.
+   Added in "DROP FUNCTION IF EXISTS" (fine in 8.3+) in
+   src/backend/slony1_funcs.sql to rectify this.
+ 
+ <li>As observed by Bernd Helmle, cloneNodePrepare returns an event ID,
+   and hence should return BIGINT
+ 
+ <li>Introduced ShouldSlonyVacuumTable() function for 8.3 so we cope with
+   differences in vacuum handling between 8.3 and 8.4+
+ 
+ <li>Fix 8.4-ism relating to subscription retries
+   <a href="http://lists.slony.info/pipermail/slony1-commit/2009-October/002728.html"> see commit notes </a>
+ 
+ <li> Doc fixes
+ <li> Fixes to integer castings - don't assume this is automagically handled
+ <li> Changed return types of functions returning event numbers <tt>bigint</tt> 
+ <li> Fixes to altperl samples and such
+ <ul>
+ <li>PostgreSQL 8.4 has been released; slonik needs to explicitly recognize it
+ 
+ <li>Add in slonikconfdump.sh tool, which generates a slonik script to duplicate
+   the configuration of a Slony-I cluster
+ 
+ <li>Significant fixes to documentation to reflect 2.0 changes
+ 
+ <li>Add "OMIT COPY" option to the Slonik "SUBSCRIBE SET" command
+ 
+ <li>Document process for Slony-I 2.0 upgrade using OMIT COPY option
+ 
+ <li>Fix to race condition where file descriptor copies were being made at
+   the wrong time in the scheduler
+ 
+ <li>Modify "testseqnames" regression test to create a whole bunch of
+   sequences to validate that things don't break down with either lots of
+   them, or where IDs are large numbers
+ 
+ <li>Change minimum debugging level to -1 to allow suppressing logging
+ 
+ <li>Bug #92 - compression of event numbers had a bug where events >
+   2^31-1 would overflow the "int" value
+ 
+ <li>Autovacuum handling changes in PostgreSQL 8.4 - we pull metadata
+   from pg_class.reloptions, instead of pg_autovacuum
+ 
+ <li>logswitch fix resolving a potential data loss + statement blocking
+   bug...
+ 
+   Before attempting to TRUNCATE the sl_log_* tables, we need to
+   successfully request an exclusive lock.  By doing so in an
+   exception block with NOWAIT option, this can "lose" gracefully.
+ 
+ <li>Add LOG_NAME_SUFFIX to altperl tools
+ 
  </ul>
  ---
***************
*** 159,204 ****
  </ul>
  ---
- Slony-I 2.0.3 rc3 available
- http://www.slony.info/downloads/2.0/source/slony1-2.0.3-rc3.tar.bz2
- 2009-11-20
- Chris Browne
- 
- Version <a href=
- "http://www.slony.info/downloads/2.0/source/slony1-2.0.3-rc3.tar.bz2">
- slony1-2.0.3-rc3.tar.bz2 </a> has been made available.
  
- <p>This fixes several things since the previous RC:
- <ul>
- <li>Updates to copyright dates on files
- 
- <li>Bug #98 - need WAIT ON parameter in slonik code generated by
-   slonik_move_set altperl script.
- 
- <li>Change default $LOGDIR, so that distros won't need to patch it.
- 
- <li>Fix LOG_NAME_SUFFIX feature. Thanks to David Fetter and Andrew Dunstan.
- 
- <li>Improve documentation on EVENT NODE for STORE NODE command
- 
- <li>SLONLOG directory changes for Red Hat-related distributions
- 
- <li>Bug #97 - insert into sl_setsync upon FAILOVER had values() clause based on the
-   pre-2.0 schema; fix to use 2.0.
- 
- <li>UPGRADE FUNCTIONS failing because functions had their return types changed.
-   Added in "DROP FUNCTION IF EXISTS" (fine in 8.3+) in
-   src/backend/slony1_funcs.sql to rectify this.
- 
- <li>As observed by Bernd Helmle, cloneNodePrepare returns an event ID,
-   and hence should return BIGINT
- 
- <li>Introduced ShouldSlonyVacuumTable() function for 8.3 so we cope with
-   differences in vacuum handling between 8.3 and 8.4+
- 
- <li>Fix 8.4-ism relating to subscription retries
-   <a href="http://lists.slony.info/pipermail/slony1-commit/2009-October/002728.html"> see commit notes </a>
- 
- </ul>
- ---
  Slony-I 1.2.17 released
  http://main.slony.info/downloads/1.2/source/slony1-1.2.17-rc.tar.bz2
--- 226,230 ----
***************
*** 240,309 ****
  </ul>
  </ul>
- ---
- Slony-I 2.0.3RC2 release candidate available
- http://main.slony.info/downloads/2.0/source/slony1-2.0.3-rc2.tar.bz2
- 2009-08-12
- Chris Browne
  
- Version <a href=
- "http://main.slony.info/downloads/2.0/source/slony1-2.0.3-rc2.tar.bz2">
- slony1-2.0.3-rc2.tar.bz2 </a> has been made available.
- 
- <p> This fixes a number of things since the previous RC:
- 
- <ul>
- <li> Doc fixes
- <li> Fixes to integer castings - don't assume this is automagically handled
- <li> Changed return types of functions returning event numbers <tt>bigint</tt> 
- <li> Fixes to altperl samples and such
- </ul>
- ---
- Slony-I 2.0.3RC release candidate available
- http://main.slony.info/downloads/2.0/source/slony1-2.0.3-rc.tar.bz2
- 2009-07-29
- Chris Browne
- 
- Version <a href=
- "http://main.slony.info/downloads/2.0/source/slony1-2.0.3-rc.tar.bz2">
- slony1-2.0.3-rc.tar.bz2 </a> has been made available.
- 
- <P>Changes since 2.0.2 are as follows:
- 
- <ul>
- <li>PostgreSQL 8.4 has been released; slonik needs to explicitly recognize it
- 
- <li>Add in slonikconfdump.sh tool, which generates a slonik script to duplicate
-   the configuration of a Slony-I cluster
- 
- <li>Significant fixes to documentation to reflect 2.0 changes
- 
- <li>Add "OMIT COPY" option to the Slonik "SUBSCRIBE SET" command
- 
- <li>Document process for Slony-I 2.0 upgrade using OMIT COPY option
- 
- <li>Fix to race condition where file descriptor copies were being made at
-   the wrong time in the scheduler
- 
- <li>Modify "testseqnames" regression test to create a whole bunch of
-   sequences to validate that things don't break down with either lots of
-   them, or where IDs are large numbers
- 
- <li>Change minimum debugging level to -1 to allow suppressing logging
- 
- <li>Bug #92 - compression of event numbers had a bug where events >
-   2^31-1 would overflow the "int" value
- 
- <li>Autovacuum handling changes in PostgreSQL 8.4 - we pull metadata
-   from pg_class.reloptions, instead of pg_autovacuum
- 
- <li>logswitch fix resolving a potential data loss + statement blocking
-   bug...
- 
-   Before attempting to TRUNCATE the sl_log_* tables, we need to
-   successfully request an exclusive lock.  By doing so in an
-   exception block with NOWAIT option, this can "lose" gracefully.
- 
- <li>Add LOG_NAME_SUFFIX to altperl tools
- </ul>
  ---
  Updated Online Docs to 2.0.2
--- 266,270 ----