Wow. First, thanks again for all your efforts, Jan. Second, I'm disappointed to hear the slony author and lead developer is leaving the slony leadership. When is that going to happen? And what does that mean with respect to your future involvement in slony?
Ed On Friday October 22 2004 7:26, Jan Wieck wrote: > Sorry folks, > > the Slony-I team has produced a great product, but the project > management (that's mostly me here) sucks big time! > > Shortly after giving Chris Browne green light for the 1.0.4 announcement > we found a way to guard against bug #896. That being a really bad one I > decided to stop the 1.0.4 release and go for 1.0.5 including that fix. > But I failed to make sure Chris, Justin and others involved in the > announcement process get the message. > > I have just committed those changes and 1.0.5 should be available later > today. > > I apologize for the confusion and look forward to retire from the > Slony-I project leadership position in order to fully focus on the > multimaster replication project Afilias has decided to put forward. > > > Jan > > On 10/21/2004 5:55 PM, Chris Browne wrote: > > The Slony-I team is proud to present the 1.0.4 release of the most > > advanced replication solution for the most advanced Open Source > > Database in the world. > > > > The release tarball is available for download > > > > http://developer.postgresql.org/~wieck/slony1/download/slony1-1.0.4.tar > >.gz > > > > There are a limited number of "new features" this release largely in > > terms of adding in the ability to move or drop tables and sequences > > from replication: > > > > - SET DROP TABLE - drops a table from replication > > - SET DROP SEQUENCE - does the same for sequences > > - SET MOVE TABLE - moves a table from one replication set to another > > - SET MOVE SEQUENCE - moves a sequence from one replication set to > > another > > > > Other changes involve smoothing out the 'sharp edges' found by early > > adopters, notably including: > > > > - Frequently vacuuming pg_listener; growth of dead tuples could hurt > > performance > > > > - A cleanup process for pg_listener resolves cases where old slon > > processes may have terminated due to network problems, leaving > > backends around holding onto event notifications > > > > - Lowered lock level on sl_event, resolving issues where pg_dump > > would block Slony-I > > > > - Purges CONFIRM entries for nodes that don't exist anymore > > > > - Substantially increased documentation > > > > - More sophisticated administration scripts > > > > - Now uses string comparison for user defined types that do not have > > a suitable comparison operation > > > > - Safer log purging > > > > - Various other bug fixes and "improved cleanliness." > > > > - As of 1.0.4, the slon replication engine refuses to work against > > any database that does not have the stored procedures for the same > > version loaded or where the shared object containing the C language > > support functions and the log trigger does not match the version > > number. in a cluster must be upgraded at once. > > > > See the HISTORY-1.0 file for a detailed list of changes. > > > > <http://slony.info/> ---------------------------(end of broadcast)--------------------------- TIP 6: Have you searched our list archives? http://archives.postgresql.org
